Details
-
Task
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
Description
We regularly see an issue with users understanding the agents, how many are required for installation and how a monitoring agent communicates. I have put together a frequent response to this, but we should have better documentation to help the customers find this.
Here is my canned response:
Hi [customer name],
Thanks for contacting the Cloud Manager support team. Looking at the error, it looks like the monitoring agent is unable to communicate with the nodes. With Cloud Manager, you only need to have one Monitoring Agent and Backup agent per group. If you look at the [agent list|
Unknown macro: {url of agents for group}], you'll see there is an active and standby for both. You can read more about the needed agents in this blog post.
In order to check connectivity, can you connect to the server the active monitoring agent is on, [server active monitoring agent is on]. Once connected to the shell, try connecting to the nodes that are unreachable with a mongo command like this:
mongo [host name]:[port]You can also try pinging the servers from [unreachable server]. If either fail, then the agent is unable to resolve the host name of the instance. Please try this on each of the nodes and let me know.