Skip to main content

Audit vs telemetry

Fact0 has two parallel pipelines:
For high-value events (LLM spend, customer data access, refunds) log to both.

Comparison Matrix

Correlation Best Practice

When executing complex multi-agent steps, always include the telemetry execution_id inside the audit event’s metadata dictionary. This enables auditors to verify that a specific action occurred (via the audit chain) and developers to inspect how it happened (via the execution DAG).

Audit log

  • Endpoints: /v1/events, /v1/events/batch
  • Storage: audit_events - SHA-256 hash chain per tenant
  • Auth: f0_live_* API keys (read/write scopes)
  • Use for: security evidence, tamper detection, regulator exports

Execution telemetry

  • Endpoints: /api/v1/executions/*
  • Storage: executions, spans, execution_events
  • Auth: f0_live_* API keys (same as audit log on Fact0 Cloud)
  • Use for: DAG visualization, replay, debugging non-deterministic agents

Span kinds (telemetry)

Audit event shape

See Event schema and Executions.