> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squasher.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Datadog HTTP

> Send logs from Datadog HTTP forwarding or pipelines into Squasher with minimal setup.

If you already route logs through Datadog and want a direct HTTP destination into Squasher, this connector gives you a clean migration path without touching application emitters.

## Setup

<Steps>
  <Step title="Create a Datadog HTTP connector in Squasher">
    Copy the destination URL, required header, and connector key from the connector details.
  </Step>

  <Step title="Create an outbound HTTP destination in Datadog">
    Configure Datadog to POST JSON or NDJSON to the Squasher connector destination. Add the
    connector key in the request headers.
  </Step>

  <Step title="Filter before forwarding">
    Start with a narrow filter such as a single service, source category, or environment. Expand
    after verification passes.
  </Step>
</Steps>

## Verify

* Trigger a test error from the filtered service.
* Confirm the connector verification succeeds in Squasher.
* Confirm the payload still includes the fields your team uses for triage.

## Migrate

For a low-risk rollout, forward the same filtered stream to both destinations for a few days, then remove the old route after dashboards and alerts are updated.

## Hot-swap

* Keep one filter per service or environment during rollout.
* Normalize severity names so Datadog values map cleanly to Squasher log levels.
* Rotate the key if multiple teams handled the temporary forwarding config.

## Agent handoff

```text theme={null}
Configure Datadog HTTP forwarding into Squasher for project <project_id>. Onboard the connector, apply the narrowest service/environment filter first, preserve severity and request fields, verify one test error, and ask before widening the filter or rotating the key.
```