Migration guide
From a cloud-provider native monitoring solution
Teams using their cloud’s built-in metrics, logs, and dashboards.
Estimated time: 2–4 weeks
Why teams switch
- →Cross-cloud or hybrid setup needs one pane of glass
- →Querying across services and accounts is clunky
- →Egress charges on raw log queries add up surprisingly fast
- →On-call routing and incident workflow are limited
What transfers as-is
- ✓CloudWatch / Monitoring metrics via a pull-side bridge — both sides keep the data
- ✓IAM-based agent authentication via a thin wrapper
- ✓Tag-based filtering becomes label-based filtering — same model, prettier syntax
What to adapt
- •Cloud-specific log query languages → Unimoni log DSL (similar shape, different keywords)
- •Cloud-tied alert routing → Unimoni channels + on-call schedules
Step by step
- 1.Run the cloud-bridge agent in pull mode — it reads cloud metrics into Unimoni
- 2.Verify the same series appear with the same numbers
- 3.Move alerts one workload at a time
- 4.Once the on-call team is comfortable, switch primary visualization
- 5.Keep the cloud-native solution as a fallback for raw debug