Skip to main content
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

1

Create an Axiom connector in Squasher

Create the connector and copy the destination URL plus connector key.
2

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

Keep structured metadata intact

Forward JSON with stable fields for message, level, service, environment, and any trace or request IDs you already rely on.

​
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