Event types

How event types shape the fields each generated event carries.

An event type describes the shape of the events a scenario step emits: the log source it imitates, the serialization format, a JSON Schema for the payload, and default field values. Event types are reusable across scenarios, and a scenario's emit step names one by id@version, such as aws.cloudtrail@v1.

What an event type defines

  • Identity — an id and version. Scenarios reference the pair, so an event type can change shape under a new version without breaking existing content.
  • Format — how the event is serialized: JSON (the default), XML for Windows event logs, or key-value text.
  • Schema — a JSON Schema for the payload. Every emitted event is validated against it, so a scenario that omits a required field or sets the wrong type fails instead of producing a malformed event.
  • Defaults — field values merged into every event before the scenario's own fields are applied.
  • Timestamp — the payload field stamped from the run's clock on every emit, and its format.
  • Correlation — the payload fields that together identify one generated event in the SIEM. Tracemill Cloud uses them to find each event after delivery and to attribute alerts to it.

Where event types come from

Event types are discovered from event-types/ directories in each content layer: the current directory, then ~/.tracemill/content/, then the installed content library. The library ships event types for AWS CloudTrail, Amazon Security Lake, Windows event logs, Microsoft 365, Microsoft Entra ID and Azure, Google Cloud audit logs, and Cisco Secure Firewall and Duo.

List the event types the CLI can see:

tracemill list event-types

An emit step that references an unknown event type is an error.

That check needs a catalog. If the CLI finds no event types at all — the content library is not installed and none are defined locally — run emits each event's fields as written, with no defaults, timestamp, or schema validation, and validate checks only the files' structure and prints a warning. Install the library with tracemill update, or point --library at one, before relying on a successful run or validation.

How fields are resolved

For each emit step, the engine starts from the event type's defaults, applies the scenario's fields on top, stamps the timestamp field, and validates the result against the schema. A scenario therefore only has to set the fields that matter to the behavior it models, plus any the schema requires and the defaults do not supply.

For the complete field reference, see the event-type schema.