After installing the mk_mongodb agent plugin on the target system, the following new
checks are available:
| Check | Description |
|---|
| mongodb_asserts | Monitors the rate of various assert types |
| mongodb_connections | Monitors the number of connections |
| mongodb_collections | Monitors the collection size |
| mongodb_counters | Monitors the number of MongoDB operations |
| mongodb_flushing | Monitors the flush time |
| mongodb_locks | Monitors the number of locks |
| mongodb_mem | Monitors the resident, virtual and mapped memory |
| mongodb_replica | Show replica information |
| mongodb_instance | Shows instance information |
Note:
If the MongoDB is running as a replica set most of the agent sections are sent to
a piggyback host named after the replication set. You can find the replica name
in the agent output under <<<<{replicaname}>>>>.
So you need to create a host named {replicaname} and execute a service discovery.
Reason:
A MongoDB replica set consists of n-Hosts. All of these hosts have the mk_mongodb plugin installed.
There is a primary host in this replica set which sends the complete plugin information.
The secondary and arbiter hosts will only send a subset of this data.
Since the primary host might change over time, we cannot put all discovered services on
the current primary host. If the host changes to secondary mode later on, all services
would be gone.
To the list of all Werks