Overview
The audit sharding diagram shows BitzOrcas.Modern’s six-category audit log sharding strategy. Each audit type (Activity, Entity, Security, Exception, IntegrationEvent, Request) writes to its own separate table, preventing any single table from growing too large and impacting query performance. Each category has an independent retention policy, enforced by a Quartz.NET scheduled job.
Key takeaways
- Six audit categories — Activity (user actions), Entity (data changes), Security (security events), Exception (errors), IntegrationEvent (integration events), Request (HTTP requests)
- Sharded storage — one table per category, physically isolated
- AuditBatchWriter — batch writer that aggregates multiple audit records before bulk insertion
- Retention policies — configurable retention days per category; expired data cleaned by JobHost
- Audit data is queried read-only through the Dapper adapter
Related
- Auditing module — audit system deep dive
- Observability — tracing and metrics