Slide 4 of 7

How to choose

Start with your database technology

The right approach depends on what database you’re running and what you need to see.

Your databaseRecommended approachWhy
MySQL or PostgreSQLDatabase ObservabilityDeepest visibility: query-level performance, explain plans, wait events
MongoDB, Redis, Memcached, Cassandra, OracleIntegrationHealth metrics with pre-built dashboards and alerts
MySQL or PostgreSQLIntegrationBasic health metrics when Database Observability isn’t an option

Decision framework

  1. Is your database MySQL or PostgreSQL? → Start with Database Observability. It gives you the deepest visibility available.
  2. Is your database supported by an integration? → Use an integration. You get health metrics, pre-built dashboards, and alerts with minimal setup.

Managed databases are supported

Database Observability works with the following self-managed databases and managed cloud services:

  • Amazon RDS and Aurora
  • Google Cloud SQL
  • Azure Database for MySQL and PostgreSQL

Script

So how do you decide which approach to use? Start with your database technology.

If you’re running MySQL or PostgreSQL, Database Observability is the recommended starting point. It gives you the deepest visibility available, down to individual queries, explain plans, and wait events. And it works with managed databases too, including Amazon RDS, Aurora, Google Cloud SQL, and Azure.

If your database isn’t supported by Database Observability, like MongoDB, Redis, Memcached, Cassandra, or Oracle, use an integration. You’ll get health metrics with pre-built dashboards and alerting rules, and most integrations take about 15 to 20 minutes to set up.

These aren’t mutually exclusive choices. You might use Database Observability for query performance on your PostgreSQL database and an integration for your Redis cache.

Previous Next