Send your logs anywhere
Webhooks for Slack, Discord or your own endpoint, and log streaming to Datadog, Splunk, Elasticsearch or Axiom, for both the audit log and network logs.
Endi · 1 min readEvery change in a workspace is already written to its audit log: a device joining, a key created, an access rule edited. Now that log can leave the dashboard, to wherever your team already looks.
Webhooks
A webhook posts each event as it happens. Send it to a Slack or Discord channel, or to your own endpoint as signed JSON, and pick which kinds of events it gets: only machines, only keys, or everything.
Each JSON request carries an X-Webhook-Signature header, an HMAC of the timestamp and body made with a secret only you and we know, so your endpoint can tell the request is real.
Log streaming
A log stream sends every event, in small batches, to Datadog, Splunk, Elasticsearch, Axiom or any HTTP collector. It's how the audit log ends up next to the rest of your logs, where your alerts and retention already live.
Network logs
Network logs are new too: which device connected to which, on which port, and how much moved. Never the content. They're off until an admin turns them on, kept for 30 days, and can be streamed like the audit log.
When a receiver is down
- Failed deliveries are retried, then logged so you can resend them.
- A destination that keeps failing pauses itself and tells you, instead of piling up.
- Destinations must use HTTPS and can't point at private addresses.