Werk #2985: MongoDB: Introduced agent plugin and some checks

Component Checks & agents
Title MongoDB: Introduced agent plugin and some checks
Date Jan 28, 2016
Checkmk Edition Checkmk Raw (CRE)
Checkmk Version 1.2.8b1 1.2.7i4
Level Trivial Change
Class New Feature
Compatibility Compatible - no manual interaction needed

After installing the mk_mongodb agent plugin on the target system, the following new checks are available:

CheckDescription
mongodb_assertsMonitors the rate of various assert types
mongodb_connectionsMonitors the number of connections
mongodb_collectionsMonitors the collection size
mongodb_countersMonitors the number of MongoDB operations
mongodb_flushingMonitors the flush time
mongodb_locksMonitors the number of locks
mongodb_memMonitors the resident, virtual and mapped memory
mongodb_replicaShow replica information
mongodb_instanceShows 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