Datadog database monitoring migration guide
If Datadog spend keeps scaling with host count, split database monitoring into a dedicated layer. This guide gives you a practical side-by-side migration path with low operational risk.
Decision matrix
Choose the path based on cost predictability, team workflow, and how much of Datadog you want to keep.
| Option | Visibility depth | Price model | Best fit |
|---|---|---|---|
| Stay on Datadog DBM | Metrics + query samples | ~$70/host/month plus add-ons | Teams fully standardized on Datadog and comfortable with host-based growth |
| Datadog infra + Basira for DB | Database-native query analytics + active queries | Datadog infra spend + $29/database/month | Teams that want Datadog for infra but predictable DB monitoring cost |
| Basira for DB monitoring | Query, table/index, replication, and lock visibility | $29/database/month | Teams moving database monitoring out of general-purpose observability tools |
Host-based Datadog spend vs Basira flat pricing
Datadog DBM pricing generally scales with monitored host count. Basira scales with database count, not vCPU or host expansion.
5 hosts / 5 databases
Datadog DBM$350/mo
Basira$145/mo
15 hosts / 10 databases
Datadog DBM$1,050/mo
Basira$290/mo
40 hosts / 20 databases
Datadog DBM$2,800/mo
Basira$580/mo
Datadog figures use a conservative `~$70/host/month` baseline from public plan pricing references.
Detailed pricing: Basira pricing.
Practical migration checklist
- 1
Inventory monitored hosts and database services
Map every Datadog host to the database workloads it represents so ownership is explicit.
- 2
Capture critical alerts and investigation workflows
List the Datadog monitors and dashboards your team actually uses during incidents.
- 3
Stand up Basira side-by-side
Deploy Basira without removing Datadog. Validate query-level parity on at least one production workload.
- 4
Run a two-week comparison window
Compare time-to-diagnosis, alert quality, and total monitoring spend before deciding cutover scope.
- 5
Cut over DB alerts first, infra later if needed
Move database alerts and runbooks first. Keep Datadog for infra/app telemetry where it still fits.
FAQ
Do we need to remove Datadog completely?
No. Common rollout: keep Datadog for infra/application telemetry, move only database monitoring first.
Can we migrate one database at a time?
Yes. The migration path is incremental. Start with one high-traffic service, validate outcomes, then roll forward.
What should we compare during a side-by-side pilot?
Compare alert quality, query-level detail during incidents, and effective monthly spend at your current host count.
Where do we start the pilot?
Create an account and deploy the agent: app.usebasira.com/signup. Setup is typically minutes.
Run the Datadog migration pilot this week
Validate visibility and cost side-by-side before committing to a full cutover.
Start Side-by-Side Pilot