Setup
1
Identify the first source group
Pick one service, environment, or log source with clear ownership and regular traffic.
2
Create the connector
Follow the Better Stack integration guide and add Squasher as an
additional destination.
3
Mirror before cutover
Keep Better Stack live while Squasher learns the same stream and your team validates grouping
and alerts.
Verify
- Compare recent error events in both tools.
- Confirm fields needed by on-call responders still exist in Squasher.
- Confirm incident noise does not increase when warning and info logs are included for context.
Migrate
- Move alert routing after Squasher issue quality is stable.
- Recreate the dashboards or saved searches your team uses during incidents.
- Repeat the process for the next source group instead of switching everything at once.
Hot-swap
- Disable duplicate notifications only after responders trust Squasher.
- Keep an overlap window through at least one deploy cycle.
- Rotate the connector key after the old forwarder is retired.