MongoDB upgrade to more than 3.0 Zabbix monitoring template changes

A description of the application scenario

Some of the MongoDB DB instances on the line upgraded to 3.0, viewing the logs of the Zabbix server constantly monitoring the host's MongoDB monitoring error

6697:20160519:222116.590 error reason for "xxxxxxxx:mongodb.discovery_status[backgroundflushing,average_ms,xxxxxxx : 1901] "changed:received value [2016-05-19t22:21:07.391+0800 E QUERY typeerror:cannot Read property ' Average_ms ' of unde Fined] is isn't suitable for value type [Numeric (float)]

Error messages are this, you can judge the errors of these monitoring host of these monitoring items to obtain the value of the problem, about MongoDB Zabbix monitoring method can refer to the following two articles

http://john88wang.blog.51cto.com/2165294/1565968

http://john88wang.blog.51cto.com/2165294/1565973

Two-monitor adjustment

Increased MongoDB storage Engine monitoring Project mongodb.discovery_status[storageengine,name,{#MONGO_HOST}]

MONGODB3.0 started supporting the Wiredtiger storage engine, and the default is Wiretiger storage engine starting from 3.2. Two storage engines MMAPV1 and Wiredtiger are supported starting from MongoDB3.0

Starting from MongoDB3.0, the MMAPV1 storage engine supports collection-level locking

Starting with MongoDB3.0, the Wiredtiger storage engine provides document-level locking and compression capabilities.

Reference Documentation:

This article is from the Linux SA John blog, so be sure to keep this source http://john88wang.blog.51cto.com/2165294/1775204

MongoDB upgrade to more than 3.0 Zabbix monitoring template changes