Skip to main content
Use this path when the Datadog Agent already tails files, container streams, or Kubernetes workloads and you want Squasher to receive the same logs without changing application code.

​
Setup

1

Create a Datadog Agent connector in Squasher

Create the connector for the target project and copy the destination URL plus connector key.
2

Add an HTTP forwarder

Configure the Datadog Agent or your existing Datadog pipeline to forward processed logs to the Squasher connector destination. Keep payloads in JSON and include the connector key header.
3

Preserve tags you care about

Keep service, host, source, env, and request identifiers when possible so searches and grouping stay familiar after cutover.

​
Verify

  • Send one error log from a known host or container.
  • Confirm the issue appears in Squasher with the expected service and environment values.
  • Confirm surrounding non-error logs appear as context, not separate incidents.

​
Migrate

Mirror one Datadog pipeline into Squasher first. Once event shape and volume look right, move alerting and saved searches one service at a time.

​
Hot-swap

  • Start with production error logs, then widen to warning and info logs.
  • Keep existing Datadog retention during overlap until on-call workflows are updated.
  • Rotate the connector key after the final switch if it lived in a shared agent template.

​
Agent handoff