Driver 01
Unpredictable billing
Invoices that jump with custom metric cardinality and log volume.
Migration playbook: Datadog → Prometheus and Grafana
Replace a growing Datadog bill with OpenTelemetry, Prometheus and Grafana, keeping the dashboards and alerts your on-call team relies on.
Migration drivers
Driver 01
Invoices that jump with custom metric cardinality and log volume.
Driver 02
Instrumentation tied to vendor agents instead of vendor-neutral OpenTelemetry.
Driver 03
Paying a premium to keep traces and logs for more than a few weeks.
Execution sequence
Each phase ends with a check you can verify — data parity, error rates, latency — and the rollback path is agreed before any traffic moves.
Deploying the OpenTelemetry Collector to receive traces, metrics and logs in OTLP.
Setting up Prometheus or VictoriaMetrics with long-term storage on object storage.
Translating Datadog dashboards and monitors into Grafana dashboards and Alertmanager rules.
Removing the Datadog agents once alert coverage has been checked.
Risk prevention
Risk 01
Exporting user IDs or transaction hashes as Prometheus labels, which exhausts memory.
Risk 02
Porting Datadog anomaly monitors to PromQL without retuning thresholds and evaluation intervals.
Risk 03
Sending uncompressed logs over public networks instead of aggregating them locally first.
Before and after
We take a baseline before any change and report the same numbers after cutover, from your own tools. They are the evidence of whether the migration worked — not figures promised in advance.
Questions
No. OpenTelemetry with Grafana Tempo or Jaeger gives you end-to-end traces and waterfall views. The UI differs, and some Datadog-specific features need a replacement or a decision to drop them.
Yes. Grafana Alerting and Prometheus Alertmanager integrate with PagerDuty, Opsgenie, Slack and custom webhooks.
Tell us about your data volume, traffic and timeline. An engineer will reply within one business day to set up a call about the migration plan and its rollback path.