Database Monitoring
4 min
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 docid\ c5froys64njazgwqe5i4m ebpf powered, zero configuration database profiling at the kernel level no database side agents or plugins needed docid\ poz9ca9hlxz2rv3qp q1q use opentelemetry sdk instrumentation for rich database query tracing with custom attributes docid\ vb7yibi2daamrzfcfwuo8 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 ✅ ✅ — 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