New in version 2.6.
SNMP is only available in MongoDB Enterprise.
MongoDB Enterprise can report system information into SNMP traps, to support 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.
Failed to Connect¶
The following in the mongod logfile:
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 mongod has appropriate permissions to open a UNIX domain socket.
Error Parsing Command Line¶
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
Error Starting SNMPAgent¶
The following line in the log file indicates that mongod cannot read the mongod.conf file:
[SNMPAgent] warning: error starting SNMPAgent as master err:1
If running on Linux, ensure mongod.conf exists in the /etc/snmp directory, and ensure that the mongod UNIX user has permission to read the mongod.conf file.
If running on Windows, ensure mongod.conf exists in C:\snmp\etc\config.