Prometheus MongoDB exporter

Application errors may be the first visible symptom of an overloaded or unhealthy MongoDB deployment. Percona’s MongoDB Exporter gathers database measurements, including supported server and replication observations, and exposes them to Prometheus for dashboards and alerts. It helps operators inspect the database behind the application. The available collectors and metric names depend on the exporter and server versions, so upgrading this historical package also requires checking the queries and alerts that consume its output.

Current guidance

The deprecated stable/prometheus-mongodb-exporter chart explicitly identifies Percona’s MongoDB exporter. Its historical app version was v0.10.0. Keep that exporter identity separate from MongoDB itself, the Helm chart, and whichever Prometheus installation scrapes the resulting endpoint.

The current upstream README documents a newer exporter implementation, MongoDB version requirements and a compatibility mode for older metric names. Existing dashboards can therefore appear empty or misleading after an image update even when Prometheus reports the target healthy. Compare metric names, labels and collector settings with each recording rule and alert you actually depend on.

Create a database user with the documented monitoring permissions, manage its URI as a secret and verify TLS requirements. Decide whether the exporter connects to one server, a replica set or multiple targets, then confirm that the expected nodes and roles are represented. Avoid enabling every expensive collection merely because it is available: measure scrape duration and database overhead. Evaluate the Prometheus community chart separately from the exporter release. No MongoDB topology or authentication setup was tested for this resource update.