Databases Monitoring
Monitor database queries and performance seamlessly.
The KloudMate Agent provides three approaches to database monitoring — from zero-configuration kernel-level profiling to deep SQL-level query analytics — so you can choose the right level of visibility for your environment.
Which approach should I use?
eBPF (DAM) is the fastest way to get started — zero configuration, no database credentials needed. For deep query analytics with execution plans and schema discovery, use Direct Database Monitoring. OpenTelemetry is ideal when your application already uses OTel SDKs and you want database spans as part of your distributed traces.
Monitoring Approaches
Database Access Monitoring (DAM)
eBPF-powered, zero-configuration database profiling at the kernel level. No database-side agents or plugins needed.
OpenTelemetry Database Monitoring
Use OpenTelemetry SDK instrumentation for rich database query tracing with custom attributes.
Direct Database Monitoring
SQL-based setup with a dedicated monitoring user for deep query metrics, execution plans, and schema discovery.
Supported Databases
| Database | eBPF (DAM) | OpenTelemetry | Direct (SQL Setup) |
|---|---|---|---|
| MySQL | ✅ | ✅ | ✅ |
| PostgreSQL | ✅ | ✅ | ✅ |
| Redis | ✅ | ✅ | — |
| Kafka | ✅ | ✅ | — |
| Elasticsearch | ✅ | ✅ | — |
| MongoDB | — | ✅ | — |
Comparison
| Feature | eBPF (DAM) | OpenTelemetry | Direct (SQL Setup) |
|---|---|---|---|
| Setup complexity | None | SDK integration | SQL scripts + agent config |
| Database credentials | Not required | Not required | Required |
| Query text | ✅ | ✅ (sanitized) | ✅ |
| Execution plans (EXPLAIN) | — | — | ✅ |
| Wait event analysis | — | — | ✅ |
| Schema discovery | — | — | ✅ |
| Distributed trace context | — | ✅ | — |
| Custom span attributes | — | ✅ | — |
| Works on managed DBs (RDS, etc.) | ✅ | ✅ | ✅ |
| Linux kernel requirement | ≥ 5.8 | None | None |