Start with the reason for leaving
New Relic is used for engineering teams needing observability and telemetry. A switch is justified only when a named workflow, cost, control, service, or portability constraint outweighs the disruption of change. Use this shortlist to select candidates for the same buyer-defined tests.
| Option | Relationship | Useful when | Evidence to collect |
|---|---|---|---|
| Datadog | Same category | engineering teams monitoring applications and infrastructure | usage-based observability pricing; test export and migration. |
| Dynatrace | Same category | enterprises comparing full-stack observability and automation | Confirm current packaging, support, security, export, and implementation scope. |
| Grafana Cloud | Same category | teams centered on open observability tooling and dashboards | Confirm current packaging, support, security, export, and implementation scope. |
Shortlist method
Start with must-have workflows, then score each vendor against pricing transparency, rollout effort, security controls, reporting needs, and exit options.
Shortlist around the job, not the brand
These options overlap with application and infrastructure observability, but they are not interchangeable. Write one test for every required job.
- Host, container, application, log, trace, and user-monitoring scope.
- Ingestion, retention, query, dashboard, and alerting requirements.
- Usage commitment, overage, retention, and support cost rules.
- Instrumentation effort, data export, and tool-consolidation assumptions.
Migration proof to request before cancellation
Options are grouped by overlapping buyer workflow. Verify current capabilities, pricing, and contract terms through the linked official sources and a representative workflow test. See the comparison methodology.