Expand description
The audit event wire shape (schema_version 1).
One AuditEvent is emitted per audited request, after the
response is known, so every event carries both who asked for
what and how it ended. The JSON produced by serde is the
contract with whoever consumes the Kafka topic: add fields freely,
but rename or remove one only together with a SCHEMA_VERSION
bump. A field with no value (None, an empty map) is left out of
the JSON rather than written as null / {}.
Nothing secret ever lands here by construction: there is no field
for a token, a password or a raw request body. Handlers describe
their operation through super::AuditNote with values they pick
explicitly.
Structs§
- Actor
- Who performed the operation, as claimed by the inbound bearer token.
- Audit
Event - One audit record. See the module docs for the stability contract.
- Client
- Where the request came from.
- Emitter
- Which manta-server instance emitted the event.
- Outcome
- How the request ended.
- Request
- The HTTP request as received.
Enums§
- Event
Kind - What kind of activity the event records.
- Verdict
- How the request ended, derived from the response status.
Constants§
- SCHEMA_
VERSION - Version of the event shape. Bump on any rename/removal.