Stratara.EventSourcing.Pipeline.CommandAudit
4.4.9
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.EventSourcing.Pipeline.CommandAudit --version 4.4.9
NuGet\Install-Package Stratara.EventSourcing.Pipeline.CommandAudit -Version 4.4.9
<PackageReference Include="Stratara.EventSourcing.Pipeline.CommandAudit" Version="4.4.9" />
<PackageVersion Include="Stratara.EventSourcing.Pipeline.CommandAudit" Version="4.4.9" />
<PackageReference Include="Stratara.EventSourcing.Pipeline.CommandAudit" />
paket add Stratara.EventSourcing.Pipeline.CommandAudit --version 4.4.9
#r "nuget: Stratara.EventSourcing.Pipeline.CommandAudit, 4.4.9"
#:package Stratara.EventSourcing.Pipeline.CommandAudit@4.4.9
#addin nuget:?package=Stratara.EventSourcing.Pipeline.CommandAudit&version=4.4.9
#tool nuget:?package=Stratara.EventSourcing.Pipeline.CommandAudit&version=4.4.9
Stratara.EventSourcing.Pipeline.CommandAudit
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
Mediator pipeline behavior that records an audit row for every dispatched command in the Stratara event-sourced stack. Both arities are provided so consumers can register a single behavior pair and have it apply to all command shapes.
What's in the box
| Type | Purpose |
|---|---|
AddCommandAuditing() |
The package's public surface — registers both behavior arities in one call. |
CommandAuditBehavior<TRequest> (internal) |
Runs the audit-write step before delegating to next() for IRequest (commands without result). |
CommandAuditBehavior<TRequest, TResult> (internal) |
Same, for IRequest<TResult> (commands with result + queries). Only records when the request also implements ICommandBase — queries flow through untouched. |
CommandAuditWriter (internal) |
Opens a transaction on IWriteUnitOfWork, writes via ICommandAuditRepository.AddAsync, commits. |
The behavior only audits commands — query requests reach the same generic interface but are filtered by the is ICommandBase check, so registering both behaviors application-wide is safe.
Quick start
// At composition time, alongside the other framework pipeline behaviors:
builder.Services.AddCommandAuditing();
That one call registers both behavior arities. The behavior types themselves are internal — they
are an implementation detail, not something to name from your composition root.
The behaviors resolve IWriteUnitOfWork from DI (ships with Stratara.EventSourcing.EntityFrameworkCore in the default deployment). No additional registration is needed.
Dependencies
Stratara.Abstractions— forIPipelineBehavior<,>,IRequest/IRequest<T>,ICommandBase,IWriteUnitOfWork,ICommandAuditRepository.JetBrains.Annotations—[UsedImplicitly]on the public behavior classes (DI-instantiated, no static call site).
At runtime an IWriteUnitOfWork implementation must be registered — typically by referencing Stratara.EventSourcing.EntityFrameworkCore and calling AddWriteStore(IConfiguration).
Security note — command payload contents
The audit row stores CommandTypeName and the serialized CommandJson of the dispatched command. Whatever fields your commands carry land in the audit table. Sensitive data (passwords, tokens, API keys, encryption material) MUST NOT live on a command record — or must be marked with [EncryptData] so the registered ISecureJsonSerializer encrypts them before persistence.
The default Stratara registration uses ISecureJsonSerializer (AES-GCM + tenant-scoped AAD) for the audit serialization, so [EncryptData]-annotated properties are protected. Plain-text properties go to disk unencrypted — treat the audit table accordingly when designing command shapes.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- JetBrains.Annotations (>= 2026.2.0)
- Stratara.Abstractions (>= 4.4.9)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.8.0 | 152 | 11/6/2026 |
| 4.7.1 | 130 | 11/5/2026 |
| 4.7.0 | 429 | 10/30/2026 |
| 4.6.1 | 112 | 10/29/2026 |
| 4.6.0 | 172 | 10/28/2026 |
| 4.5.0 | 261 | 10/28/2026 |
| 4.4.10 | 201 | 10/26/2026 |
| 4.4.9 | 106 | 10/26/2026 |
| 4.4.8 | 244 | 10/24/2026 |
| 4.4.7 | 118 | 10/23/2026 |
| 4.4.6 | 213 | 10/22/2026 |
| 4.4.5 | 283 | 10/14/2026 |
| 4.4.4 | 295 | 10/10/2026 |
| 4.4.3 | 138 | 10/10/2026 |
| 4.4.2 | 389 | 10/2/2026 |
| 4.4.1 | 362 | 9/29/2026 |
| 4.4.0 | 138 | 9/27/2026 |
| 4.3.1 | 141 | 9/25/2026 |
| 4.3.0 | 299 | 9/23/2026 |
| 4.2.0 | 144 | 9/18/2026 |
A fix for hosts on the Orleans execution model. A host that removed or renamed a projection no longer has that
projection's store readers come back on every start and fail each entry; they retire once, as a saga's readers do. A
retired store reader now logs its retirement once instead of three times, and leaves no reminder error behind. No
API change, no schema change and no migration.
### Fixed
- **A reader of a removed projection retires.** On the Orleans execution model, a host that removed or renamed a
projection kept the keep-alive reminders of its store readers. On every start of the silo they brought the readers
back, and each one read the next entry of its partition, failed it because no projection of its name was
registered, and tried again on the next tick, without end — a warning per partition and entry. Such a reader now
retires the first time it is brought back, as a saga's reader already did: it unregisters its keep-alive, logs
`117_136` `UnregisteredProjectionReaderRetired` (Information) once, reads nothing and deactivates. Its checkpoints
stay, so a projection registered again resumes where it stopped; *Operate the Orleans execution model* says how to
delete them. In a rolling deployment that adds a projection, a reader that lands on a silo of the earlier version
refuses a rebuild's or a replay's pause, which then fails naming it, and a wait counts its partition as behind.
- **A retired store reader logs its retirement once.** A reader that retired as it was activated — of a partition
beyond a lowered partition count, or of a saga the silo no longer registers — deactivated before it answered the
call that activated it. Orleans forwarded that call to a new activation, which retired again, so the retirement was
logged three times per reader and the keep-alive tick ended in `Could not deliver reminder tick` at Error. The
reader now answers the call first and deactivates after it.