MongoDB Enterprise can provide database metrics via SNMP, in support of centralized data collection and aggregation. This document identifies common problems you may encounter when deploying MongoDB Enterprise with SNMP as well as possible solutions for these issues.
If you receive the following error message when trying to monitor with SNMP:
<Timestamp> F CONTROL [main] Failed global initialization: Bad Value: snmp.subagent is not allowed when snmp.disabled is specified
By default, SNMP access to
mongod instances is enabled.
Starting in MongoDB 4.0.6, you can disable SNMP access using either
or the configuration file option
The following in the
Warning: Failed to connect to the agentx master agent
AgentX is the SNMP agent extensibility protocol defined in Internet RFC 2741. It explains how to define additional data to monitor over SNMP. When MongoDB fails to connect to the agentx master agent, use the following procedure to ensure that the SNMP subagent can connect properly to the SNMP master.
Make sure the master agent is running.
Compare the SNMP master's configuration file with the subagent configuration file. Ensure that the agentx socket definition is the same between the two.
Check the SNMP configuration files to see if they specify using UNIX Domain Sockets. If so, confirm that the
mongodhas appropriate permissions to open a UNIX domain socket.
One of the following errors at the command line:
Error parsing command line: unknown option snmp-master try 'mongod --help' for more information
Error parsing command line: unknown option snmp-subagent try 'mongod --help' for more information
MongoDB Enterprise on macOS does not include support for SNMP due to SERVER-29352.
The following line in the log file indicates
mongod cannot read the
[SNMPAgent] warning: error starting SNMPAgent as master err:1
If running on Linux, ensure
mongod.conf exists in the
directory, and ensure that the
mongod UNIX user has
permission to read the
If running on Windows, ensure
mongod.conf exists in