Integrations

Send urgent control events to the systems your team already watches.

read 11:02:52 UTC

Nothing is forwarded yet

Add a webhook, a Splunk HEC endpoint or a Datadog intake, and every refusal, hold, halt and anchor failure on this log is posted within seconds of being chained — signed, retried, and listed here.

Add a destination

Delivery log

every attempt, newest first · the last 50

When	Event	Destination	Attempt	Status
Nothing has been queued for delivery yet.

Verifying a webhook
What this means
The full scheme, the Splunk and Datadog formats, and the retry ladder — 30 seconds, then 2, 10 and 30 minutes, then 2 and 6 hours; seven attempts over about nine hours — are in the docs: Webhooks & SIEM.

what your receiver checks

x-auditant-timestamp	unix seconds; reject if older than 300
x-auditant-signature	HMAC-SHA256 over ${timestamp}.${rawBody}, under the secret shown once when the destination was added
x-auditant-delivery	stable across retries — your idempotency key

Syslog and S3 export are on the roadmap and are not built. Everything listed above is what leaves this control plane today.

Delivery log

Verifying a webhookⓘWhat this meansCloseThe full scheme, the Splunk and Datadog formats, and the retry ladder — 30 seconds, then 2, 10 and 30 minutes, then 2 and 6 hours; seven attempts over about nine hours — are in the docs: Webhooks & SIEM.

Verifying a webhook
What this means
The full scheme, the Splunk and Datadog formats, and the retry ladder — 30 seconds, then 2, 10 and 30 minutes, then 2 and 6 hours; seven attempts over about nine hours — are in the docs: Webhooks & SIEM.