Skip to main content
If Axiom is already your log destination, the safest migration is to duplicate the stream into Squasher first, then move teams over once search, grouping, and alerting are in place.

​
Setup

1

Choose the forwarding point

Use the place in your current pipeline where events are already structured and ready to send downstream.
2

Create the Squasher connector

Follow the Axiom integration guide and keep the Squasher destination in parallel with Axiom during rollout.
3

Start narrow

Forward a single service or environment first so you can validate grouping and field mapping before expanding.

​
Verify

  • Compare one event in Axiom and Squasher side by side.
  • Confirm error-level logs become issues and lower-severity logs remain searchable context.
  • Confirm the time range and timestamps line up cleanly.

​
Migrate

  • Rebuild the searches and alerts your team uses most often.
  • Train responders on issue grouping and AI triage in Squasher before disabling the old workflow.
  • Remove Axiom forwarding only after the overlap window covers normal incidents and deploys.

​
Hot-swap

  • Keep field names stable during the overlap window.
  • Avoid changing parsing rules and destinations at the same time.
  • Rotate the Squasher connector key after the old branch is removed.

​
Agent handoff