DKNet
Publish audit batches
Part of DKNet.EfCore.AuditLogs. The Quick Start publisher implements IAuditLogPublisher.PublishAsync. To register several sinks, replace its one-call publisher registration with:
services.AddEfCoreAuditHook<DemoDb>();
services.AddKeyedScoped<IAuditLogPublisher, ConsolePublisher>(typeof(DemoDb).FullName!);
Add another keyed scoped registration for each additional publisher implementation. Resolve the registered sinks with scope.ServiceProvider.GetAuditLogPublishers<DemoDb>() when needed. AddEfCoreAuditLogs<TDbContext, TPublisher>() combines publisher and hook registration and ignores a duplicate of the same publisher for the same key.
🧱 Where it fits
The package architecture places the publisher adapter at the host boundary. Your implementation owns persistence, transport and retention; this package owns capture and invocation.
⚠️ Gotchas & limits
- Publishing exceptions, including cancellation exceptions from a publisher, are caught per sink. The save can return successfully with a lost audit batch. There is no retry or outbox here.
- The structured failure message includes publisher type, entity names and entry count, rather than serializing the batch; the exception is still supplied to the logger.
- Publisher lookup uses the runtime context type name. Register against the concrete context type used at runtime.
- Do not promise atomicity between entity persistence and an external audit sink; an application requiring that needs a transactional design of its own.