Documentation menuCustom store
Custom store
Use another database by implementing AuditStore.
interface AuditStore {
insert(events: AuditEvent[]): Promise<void>
query(query: StoreQuery): Promise<AuditEvent[]>
get(id: string): Promise<AuditEvent | null>
count?(query: StoreFilter, groupBy?: AuditGroupBy): Promise<AuditGroupCount[]>
deleteBefore?(before: string, tenantId?: string | null): Promise<number>
rewriteActor?(actorId: string, actor: AuditActor): Promise<number>
}
Since 2.0 an event can carry outcome and correlationId, and StoreQuery can filter by both. Your store has to save and return them, and a filter outcome: "success" has to match events that have no outcome (everything recorded before 2.0). The conformance suite checks all of this.
query receives a validated StoreQuery and must return at most limit events ordered by occurredAt descending, then id descending. before is the keyset position for paging: return only events strictly older than (occurredAt, id).
The functions matches(event, query) and compareEvents(a, b) from the core package are the reference semantics; the test suite of the built-in stores runs the same cases against memory, SQLite, Postgres, MySQL and MariaDB.
Conformance suite
@sweberdev/logarithm/testing ships the same checks, so you can prove that your store behaves like the built-in ones: newest-first order, field round trip, tenant isolation (a scoped log cannot be widened), filters, case-insensitive search with literal wildcards, keyset paging across events in the same millisecond, counts and grouping, and, when your store implements them, retention and erasure.
import { storeConformanceChecks } from "@sweberdev/logarithm/testing"
import { describe, it } from "vitest" // or jest, node:test
describe("my store", () => {
for (const check of storeConformanceChecks) {
it(check.name, () => check.run(async () => {
await truncateTable()
return myStore(client)
}))
}
})
The factory is called before every check and must return an empty store. A failing check throws a ConformanceError that names what differed. Without a test runner, runStoreConformance(factory) runs everything and returns the failures.
count is optional. It receives the same filters as query without limit and before, and returns one { key, count } per group (key is the UTC day YYYY-MM-DD, the action or the actor id) in any order, or a single { key: "", count } without groupBy. Without it, audit.count() pages through query, which is correct but slower. countEvents(events, filter, groupBy) is the reference implementation.
deleteBefore and rewriteActor are optional; retention and erasure in Logarithm Pro need them.