MongoDB OpenTelemetry Assets

MongoDB is a document-oriented NoSQL database that stores data as flexible JSON-like (BSON) documents. It is widely deployed for high-throughput, low-latency workloads and supports horizontal scaling through sharding and high availability through replica sets.

This content pack provides dashboards, alert rules, and SLO templates for MongoDB monitoring. The assets use metrics from the OpenTelemetry MongoDB receiver (mongodbreceiver) and cover operation throughput, latency, cache efficiency, connection utilization, memory, storage, cursor health, and session counts.

The MongoDB OpenTelemetry assets have been tested with:

• OpenTelemetry MongoDB receiver v0.146.1
• MongoDB 4.0, 5.0, 6.0, 7.0

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

Before collecting data, you must configure MongoDB to allow the collector to connect and gather metrics. Create a dedicated user with the clusterMonitor role, which grants access to serverStatus and dbStats:

use admin
db.createUser({
  user: "otel_monitor",
  pwd: "your_password",
  roles: [ { role: "clusterMonitor", db: "admin" } ]
})
		

Configure the OpenTelemetry Collector (or Elastic OpenTelemetry Collector) to receive MongoDB metrics and export them to Elasticsearch. The following example uses the mongodbreceiver with the elasticsearch/otel exporter.

All metrics consumed by the dashboards, alerts, and SLOs are enabled by default in the receiver — no optional metrics need to be turned on.

Placeholders

receivers:
  mongodb:
    hosts:
      - endpoint: <MONGODB_ENDPOINT>
    username: <MONGODB_USER>
    password: ${env:MONGODB_PASSWORD}
    collection_interval: 1m
    direct_connection: true

processors:
  attributes/mongodb:
    actions:
      - key: mongodb.instance
        value: <MONGODB_INSTANCE>
        action: upsert

exporters:
  elasticsearch/otel:
    endpoints: [<ES_ENDPOINT>]
    mapping:
      mode: otel

service:
  pipelines:
    metrics/mongodb:
      receivers: [mongodb]
      processors: [attributes/mongodb]
      exporters: [elasticsearch/otel]
		

The attributes/mongodb processor adds the mongodb.instance attribute used by the dashboard Server control. Set <MONGODB_INSTANCE> to the same host:port you use in <MONGODB_ENDPOINT>.

Note: direct_connection: true is required for standalone MongoDB instances; for replica sets, remove it and list all hosts. For unauthenticated local MongoDB, omit username and password. For production, configure Elasticsearch authentication and TLS as described in the Elasticsearch exporter documentation.

For the full list of settings exposed for the receiver, refer to the configuration section.

Refer to the OpenTelemetry MongoDB receiver's documentation for the complete list of metrics collected.

SLO templates are available in Stack 9.4.0 and later. On Stack 9.3.x, the package can still be installed, but the SLO templates are not shown in the Assets UI.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.

← →

×

×

×