Setup
1
Inventory current Datadog coverage
List the services, environments, saved searches, and monitors you need to preserve during
migration.
2
Create the right Squasher connector
Use either the Datadog Agent or Datadog
HTTP setup depending on where you can forward traffic today.
3
Mirror one stream first
Start with one service or environment so you can compare event shape, volume, and grouping
before wider rollout.
Verify
- Compare error counts across the overlap window.
- Check that
service,env, and request identifiers still exist in Squasher. - Confirm the highest-volume incident groups look correct and are not over-grouped.
Migrate
- Move monitor ownership one service at a time.
- Recreate the most important saved views and notification routes in Squasher before disabling the old ones.
- Keep the overlap window long enough to cover normal traffic and at least one deploy.
Hot-swap
- Disable duplicate paging only after Squasher notifications are stable.
- Rotate connector keys after the final Datadog forwarder is removed.
- Add SDK coverage later if you want richer stack, user, and release context.