> ## 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.

# Better Stack

> Forward Better Stack logs into Squasher for rollout, comparison, or full migration.

If Better Stack already receives your application or platform logs, you can forward the same stream into Squasher and move triage workflows over in stages.

## Setup

<Steps>
  <Step title="Create a Better Stack connector in Squasher">
    Create the connector in your Squasher project and copy the destination details.
  </Step>

  <Step title="Add Squasher as an HTTP destination">
    In your Better Stack pipeline or forwarding rule, send JSON payloads to the Squasher connector
    URL and include the connector key header.
  </Step>

  <Step title="Start with one source">
    Begin with a single service, environment, or source category so you can verify shape and alert
    volume before broad rollout.
  </Step>
</Steps>

## Verify

* Emit a test error and confirm it lands in Squasher quickly.
* Confirm fields like `service`, `host`, and request IDs are still searchable.
* Confirm info-level logs stay attached as context instead of creating incidents.

## Migrate

Run Better Stack and Squasher side by side long enough for on-call responders to trust the new workflow, then move alerts and disable the old forwarding path.

## Hot-swap

* Migrate one source group at a time.
* Keep filters conservative until you understand volume in Squasher.
* Rotate the connector key after final cutover.

## Agent handoff

```text theme={null}
Forward one Better Stack source into Squasher for project <project_id>. Create or onboard the connector, keep the first source narrow, verify service/host/request fields, compare event volume, and ask before replacing alert routing or rotating keys.
```