Bring your own logs

What you get

• Datadog, any OpenTelemetry collector or any HTTPS endpoint
• Every line from every app and environment
• More than one destination at a time
• A test line before a destination is saved
• Lines that were missed sent once it answers again
• Owners told when sending keeps failing
• Logs still searchable in Whisk as well

How it works

An owner adds a destination in the dashboard settings. Whisk sends it a test line first and saves it only if the destination accepts it. The API key or headers are stored encrypted, and only their names are shown afterwards.

Every few seconds, Whisk sends new lines in batches, labelled with the app, the environment and the stream. If the destination refuses a batch, Whisk retries with growing waits and then sends what was missed. After 15 minutes of failures, the owners are told and the dashboard shows the problem.

The OpenTelemetry option uses OpenTelemetry's open standard for logs, which Grafana Cloud, Honeycomb and New Relic accept. The same lines stay in log search. Bring your own logs is on the Business and Agency plans.

Example

A building products manufacturer's IT team watches all its systems in Datadog. It adds Whisk as one more source, so errors from its dealer portal and warranty claims app show beside its other alerts.

For your coding agent

whisk logs forwarding
whisk logs forwarding test <destination id>

An owner adds and removes destinations; an agent checks how sending is going and sends a test line. Every command is in the CLI reference.