Migrate from Better Stack

​

What moves and what does not

​

Run both tools side by side

​

Send a copy of your logs

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

[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}"

​

Move alerts and on-call

1. Recreate the uptime monitors. The dashboard creates HTTP monitors: select Monitors in the sidebar, then New monitor. Create heartbeats and other check types with the Monitors API.
2. Recreate each status page: select Status pages in the sidebar, then Create status page. See Status pages.
3. Recreate the notification channels as destinations and routes: Slack, email, Telegram, webhook, or PagerDuty.
4. Recreate the on-call calendars: select On-call in the sidebar, then Create schedule. See On-call.

​

Check parity

• The number of log lines and error lines per service each hour.
• The fields that responders search on, such as service, host, and request ID.
• Each monitor. Stop a test endpoint, and check that both tools open an incident.
• Each heartbeat. Skip one run of a job, and check that Squasher opens an incident.

​

Turn off Better Stack

1. Point your jobs at the Squasher heartbeat URLs, if you have not done it yet.
2. Move your public status page domain to Squasher. See Custom domains.
3. Turn off the Better Stack monitors and paging.
4. Remove the Better Stack destination from your log shipper or host.

​

Next steps

Add monitors

Learn how checks, heartbeats, and incidents work.

Status pages

Publish incidents and component status.

Set up notifications

Send incidents to Slack, email, or PagerDuty.

Choose how to send data

Compare SDKs, log drains, and OpenTelemetry.