Supported databases
PostgreSQL
pgMySQL
mysql / mysql2MariaDB
mariadbMongoDB
mongodb / mongooseRedis
redis / ioredisValkey
iovalkeyElasticsearch
elasticsearch / @elastic/elasticsearchOpenSearch
@opensearch-project/opensearchCassandra
cassandra-driverCouchBase
couchbaseMemcached
memcachedOracleDB
oracledbSQL Server
tediousPrisma
@prisma/clientKnex
knexAerospike
aerospikeCommon configuration options
All database plugins extend theInstrumentation interface and accept:
| Option | Type | Default | Description |
|---|---|---|---|
enabled | boolean | true | Enable the plugin. |
service | string | (params) => string | — | Override the service name. Pass a function to derive the name from connection parameters. |
measured | boolean | — | Whether to measure the span for metrics. |
PostgreSQL (pg)
dbmPropagationMode correlates APM traces with Database Monitoring query samples. Valid values are 'disabled' (default), 'service', and 'full'.
MySQL and MySQL2
mariadb uses the same configuration interface as mysql.
MongoDB
Themongodb-core plugin instruments both the low-level mongodb-core driver and the mongodb package directly. The mongoose plugin provides additional Mongoose-specific spans.
Redis
- redis
- ioredis
- iovalkey
allowlist and blocklist filter by command name (lowercase), not by URL.
Elasticsearch and OpenSearch
OracleDB
Prisma
Database Monitoring (DBM) integration
To correlate APM traces with Database Monitoring query samples, setdbmPropagationMode at the tracer level or per-plugin:
| Mode | Description |
|---|---|
'disabled' | No SQL comment injected (default). |
'service' | Injects service name only. |
'full' | Injects full trace context including trace and span IDs. |
