Database Monitoring

SigNoz monitors your databases across three layers of telemetry:

• Metrics: connection counts, query throughput, cache hit ratios, replication lag, and disk usage, collected by OpenTelemetry Collector receivers or by scraping the database's Prometheus exporter.
• Logs: error logs, slow query logs, and audit logs, parsed into structured fields you can search and alert on.
• Traces: database calls captured as spans, when your instrumentation emits the required span attributes. This traces a slow endpoint to the query behind it, when the instrumentation records query text.

Pick your database below. If you run a managed database from a cloud provider, use the cloud sections: those integrations pull metrics from the provider's monitoring API instead of connecting to the database directly.

Find Your Database

Filter by category, or browse everything: self-hosted engines, AWS, GCP, Azure, and DBaaS platforms. Azure integrations use the one-click path; see one-click Azure integrations for the shared setup.

Connection Pooling and Kubernetes Operators

Tracing Database Queries

Database metrics show cluster health, but they cannot tell you which application request caused a spike. Once your application emits database spans with the required attributes, SigNoz captures each call and aggregates them per database and per operation.

Dashboard Templates

Import a pre-built dashboard instead of building panels from scratch. See importing a dashboard for the steps.

Setting Up Alerts

Once metrics are flowing, create alerts on the signals that matter for your database: connection saturation, replication lag, disk usage, or slow query volume. See creating alert rules to get started.