MongoDB (local or remote monitoring) extension
- Latest Dynatrace
- Extension
- Published Oct 27, 2025
Monitor your MongoDB servers either locally or remotely!
Get started
Overview
Connect your MongoDB servers either remotely and locally. A collective batch of data is gathered every minute by this extension and sent to the Dynatrace platform for detailed analysis.
Use cases
- Monitor database traffic for optimization plan.
- Monitor database operations with a comprehensive dashboard.
- Take pre-emptive measures to avoid service degradations.
Requirements
- Depending on your deployment, one of the folowing is true
- Dynatrace OneAgent is installed on you MongoDB Server.
- Dynatrace ActiveGate is installed and with network access to your MongoDB Server.
- A MongoDB user with
serverStatus@admin,listDatabases, anddbStatspermissions. The MongoDB Built In Cluster Monitor Role has these permissions already set up.
Activation and setup
- Enable the extension via the Dynatrace Hub.
- Choose to monitor remotely via an ActiveGate group or locally via the OneAgent.
- Enter the configuration and credentials.
- Review the data in the included dashboard.
Details
Along with the username and password you can configure the extension to:
-
Use a different Authentication Database (sets the
authSourceproperty in the connection string). -
Add a path to a CA PEM File (sets the
tlsCAFileargument of the MongoClient). -
Add a path to a Client Certificate (sets the
tlsCertificateKeyFileof the MongoClient).These file paths need to be accessible on all ActiveGates in the group or locally on the OneAgent Host
-
Select between MongoDB Auth Mechanisms:
SCRAM-SHA-1,SCRAM-SHA-256,PLAIN,DEFAULT.If no mechanism is specified, PyMongo will automatically use a default value depending on MondoDB version.
- MondoDB version 3.6
SCRAM-SHA-1 - MondoDB version 4.0+
SCRAM-SHA-1orSCRAM-SHA-256
- MondoDB version 3.6
FAQ
What is the Custom Metric Usage of this extension?
The formula for consumption of the extension is:
Per connected process/port: (17 + 5 * <# of Databases>)
Activating the extension locally consumes the included metrics per host unit.
Feature sets
When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
wiredTiger
| Metric name | Metric key | Description |
|---|---|---|
| Cache - Pages Requested | mongodb.cache.pages_requested | Number of pages reqeusted from the cache |
| Cache - Pages Read | mongodb.cache.pages_read | Number of pages read into the cache |
locks
| Metric name | Metric key | Description |
|---|---|---|
| Locks - Current Global Queue | mongodb.locks.global_current_queue | The number of operations queued because of a lock. |
| Locks - Global Total Time | mongodb.locks.global_total_time | The time, in microseconds, since the database last started and created the globalLock. This is roughly equivalent to total server uptime. |
| Locks - Current Global Acquired Locks | mongodb.locks.global_acquire | Number of times the lock was acquired in the specified mode. |
| Locks - Current Global Aqcuired Waits | mongodb.locks.global_acquire_wait | Number of times the lock acquisitions encountered waits because the locks were held in a conflicting mode. |
| Locks - Global Time Acquired (Microseconds) | mongodb.locks.global_time_acquire | Cumulative wait time in microseconds for the lock acquisitions. |
| Locks - Current Global Deadlocks | mongodb.locks.global_deadlocks | Number of times the lock acquisitions encountered deadlocks. |
default
| Metric name | Metric key | Description |
|---|---|---|
| Current connections | mongodb.current_connections | — |
| Available connections | mongodb.available_connections | — |
| Insert operations | mongodb.insert_operations2.count | — |
| Query operations | mongodb.query_operations2.count | — |
| Update operations | mongodb.update_operations2.count | — |
| Delete operations | mongodb.delete_operations2.count | — |
| Getmore operations | mongodb.getmore_operations2.count | — |
| Command operations | mongodb.command_operations2.count | — |
| Resident memory | mongodb.resident_memory | — |
| Virtual memory | mongodb.virtual_memory | — |
| Current queue | mongodb.current_queue | — |
| Active clients | mongodb.active_clients | — |
| Regular asserts | mongodb.regular_asserts2.count | — |
| Warning asserts | mongodb.warning_asserts2.count | — |
| Message asserts | mongodb.message_asserts2.count | — |
| User asserts | mongodb.user_asserts2.count | — |
| Rollover asserts | mongodb.rollover_asserts2.count | — |
| Page Faults | mongodb.page_faults | The total number of page faults |
| Uptime | mongodb.uptime | The number of seconds that the MongoDB process has been active. |
| Objects | mongodb.db.objects | — |
| Indexes | mongodb.db.indexes | — |
| Data size | mongodb.db.db_data_size | — |
| Storage size | mongodb.db.db_storage_size | — |
| Index size | mongodb.db.db_index_size | — |
replicaSet
| Metric name | Metric key | Description |
|---|---|---|
| Replica Set - Oplog Size | mongodb.rs.oplog_size | The range between the earliest and latest oplog entires |
| Replica Set - Oplog Window | mongodb.rs.oplog_window | The time window covered by the oplog (Replication headroom) |
