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

# Axiom

> Mirror logs from Axiom into Squasher while keeping migration and verification simple.

Axiom is often already sitting behind apps, workers, or pipeline collectors. Squasher connectors let you mirror that stream during migration so you can compare volume, fields, and issue quality before cutover.

## Setup

<Steps>
  <Step title="Create an Axiom connector in Squasher">
    Create the connector and copy the destination URL plus connector key.
  </Step>

  <Step title="Forward the stream from your existing pipeline">
    Add Squasher as an additional HTTP destination from the part of your pipeline that already
    formats Axiom-bound events.
  </Step>

  <Step title="Keep structured metadata intact">
    Forward JSON with stable fields for `message`, `level`, `service`, `environment`, and any trace
    or request IDs you already rely on.
  </Step>
</Steps>

## Verify

* Send a test event from a service with known metadata.
* Confirm Squasher groups the error correctly and shows nearby logs as context.
* Compare one event in both tools to make sure important fields survived the forward.

## Migrate

Run both destinations in parallel first. Once Squasher has enough production traffic for confidence, switch alerts, runbooks, and dashboards to Squasher and then remove the extra destination.

## Hot-swap

* Keep timestamps in ISO 8601 when possible.
* Reduce duplicate enrichment during overlap so events do not become noisy.
* Rotate the connector key after removing the temporary mirror path.

## Agent handoff

```text theme={null}
Mirror Axiom-bound logs into Squasher for project <project_id>. Create or onboard the Axiom connector, start with one service or environment, send one error-level test event, compare fields in both systems, and ask before rotating the connector key or removing the old destination.
```