OpenTelemetry Database Monitoring

in addition to the ebpf based database access monitoring (dam), you can use opentelemetry sdk instrumentation to capture detailed database query traces with custom attributes how it works opentelemetry auto instrumentation agents and sdks provide library specific hooks that capture database operations as trace spans these spans include sql query text (sanitized) database system and name operation type (select, insert, update, delete) duration and status connection details when to use when you need rich, library specific database query details when you want custom attributes on database spans when your application already uses opentelemetry sdks when combined docid\ jgzovknht8vf3phbc3dud for the business context supported database libraries language libraries auto instrumented java jdbc, hibernate, spring data python sqlalchemy, psycopg2, pymysql, django orm node js pg, mysql2, mongoose, prisma net entity framework, npgsql, mysqlconnector go database/sql, gorm, pgx configuration configure your opentelemetry sdk to export to the kloudmate agent otlp endpoint otel exporter otlp endpoint="http //localhost 4318" otel service name="your service name" database spans will automatically be captured when using supported auto instrumentation libraries for zero configuration kernel level profiling, see database access monitoring (dam) for deep query analytics with execution plans and schema discovery, see direct database monitoring