Migrate from Axiom

Squasher has no importer for Axiom. You send a second copy of your events from the tool that ships them today, and you recreate queries, dashboards, and monitors by hand.

What moves and what does not

In Axiom	In Squasher	Notes
Log events	Logs	Send a copy from your log shipper or host. Error-level events open issues.
Traces	Traces	Point your OTLP exporter at Squasher. See OpenTelemetry.
Past events in datasets	Not imported	Squasher starts with the events that you send after the switch.
APL queries and saved queries	Not imported	Rewrite the queries that your team uses in Logs.
Dashboards	Dashboards	Recreate them by hand or as code.
Monitors	Query monitors	Recreate them with the Monitors API.
Notifiers	Destinations	Slack, email, Telegram, webhook, or PagerDuty. See Notifications.

Run both tools side by side

Keep Axiom running, and add Squasher as a second destination in the tool that ships your events. Axiom keeps its data. Leave your Axiom monitors on until the checks in Check parity pass.

Send a copy of your events

Next.js
Node.js
Log drains
OpenTelemetry
Vector

If you send logs from Next.js with an Axiom library, add the Next.js SDK next to it. The SDK sends errors with stack traces.

Add a Squasher exporter to your Collector, and add it to each pipeline next to the exporter that you use today:

otel-collector-config.yaml

exporters:
  otlphttp/squasher:
    endpoint: https://ingest.squasher.ai
    headers:
      x-squasher-key: ${env:SQUASHER_API_KEY}

Add a sink to your Vector config. The transform sets a level on events that have none, because Squasher treats an event without level as an error.

vector.toml

[transforms.squasher_level]
type = "remap"
inputs = ["app_logs"]
source = '''
if !exists(.level) { .level = "info" }
'''

[sinks.squasher]
type = "http"
inputs = ["squasher_level"]
uri = "https://ingest.squasher.ai/v1/ingest/${SQUASHER_PROJECT_ID}"
encoding.codec = "json"
request.headers.x-squasher-key = "${SQUASHER_API_KEY}"

Replace app_logs with the name of your source. Each event needs a message field.

Move alerts

Recreate each Axiom monitor as a query monitor with the Monitors API. Query monitors check a count or a value from your logs, metrics, or latency over a time window.
Recreate each notifier as a destination and a route.
Test each monitor once, and check that the alert reaches the right channel.

Check parity

Compare the two tools for at least one week that includes a deploy:

The number of events and error events per service each hour.
One event in both tools. Check that the fields that you search on are there.
The timestamps. Squasher reads ISO 8601 strings and Unix time numbers.
The issues that Squasher opened for the week, against the errors that you saw in Axiom.

Turn off Axiom

Turn off the Axiom monitors after the Squasher monitors have fired correctly.
Remove the Axiom destination from your log shipper or host.
Export any past data that you must keep before your Axiom retention ends.

Next steps

OpenTelemetry

Send logs, traces, and metrics from any language.

Add monitors

Learn how query monitors and incidents work.

Dashboards as code

Define dashboards in files and review them.

Set up notifications

Send incidents to Slack, email, or PagerDuty.

Get started

Guides

Migrate from Axiom

What moves and what does not

Run both tools side by side

Send a copy of your events

Move alerts

Check parity

Turn off Axiom

Next steps

OpenTelemetry

Add monitors

Dashboards as code

Set up notifications

​What moves and what does not

​Run both tools side by side

​Send a copy of your events

​Move alerts

​Check parity

​Turn off Axiom

​Next steps

OpenTelemetry

Add monitors

Dashboards as code

Set up notifications

What moves and what does not

Run both tools side by side

Send a copy of your events

Move alerts

Check parity

Turn off Axiom

Next steps