From New Relic database monitoring to Obsfly

• Usage-based pricing is unpredictable on chatty DB workloads.
• Database-specific UX feels grafted onto APM rather than purpose-built.
• No BYOC.
• Limited per-engine depth on Mongo / Redis / ClickHouse.

Fairness signal — useful in renewal conversations.

• If you already use New Relic for APM, the correlation is good.
• Free tier is generous for small teams.

1. Step 1

   Inventory current New Relic data ingest

   Pull NR's data-usage UI to see GB/mo of DB telemetry — that's the cost driver.

2. Step 2

   Install Obsfly agent

   Go binary, runs alongside the New Relic infrastructure agent.

3. Step 3

   Rebuild critical dashboards

   Per-engine views ship fully formed. Custom panels migrate via NRQL → PromQL conversion.

4. Step 4

   Migrate alerts

   NR alerts → Obsfly rules. Forecast-violation rules cover the seasonality cases NR's anomaly mode struggles with.

• Watch billing month-end during overlap — usage-based bills spike if you double-instrument.
• Keep NR APM; Obsfly is DB-only.

What about New Relic AI Monitoring?

Obsfly's AI Insights are query-grounded with your schema and last 50 plans — narrower scope, deeper recommendations.