- Alerts and Monitoring >
- Alerts >
- Alert Resolutions >
- Host Down
Host Down¶
Description¶
At time T
, the Monitoring Agent on host X
had not detected a mongod
process running on host Y
port Z
for A
minutes.
Common Triggers¶
- The mongod process could not be reached because of a network issue.
- The mongod process is not running.
- The host is powered off.
Possible Solutions¶
Verify network communication between the host running the Monitoring Agent and the host that is listed as down. One way to do this is through the mongo shell:
If connecting from the mongo shell fails, try a basic ping test:
Verify the mongod process is running:
If the process was installed from
deb
orrpm
package, query the service manager for the status:Alternatively, you can use
ps
:
Notes¶
The Host Down
alert should not be used to detect all occurrences of a
host rebooting. The alert is triggered only if the host is seen as down at
the instant that the Monitoring Agent runs the check. The interval between
checks can vary from 1 to 3 minutes.
Documentation¶
Host is down
alert condition