[DOCS-2497] MMS Host Down Alerts are "per group" not "per agent" Created: 09/Jan/14  Updated: 02/Sep/14  Resolved: 24/Jan/14

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: v1.3.0

Type: Task Priority: Major - P3
Reporter: David Hows Assignee: Tim Slavin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

http://mms.mongodb.com/help/monitoring/faq/


Issue Links:
Related
Participants:
Days since reply: 10 years, 5 weeks, 6 days ago

 Description   

http://mms.mongodb.com/help/monitoring/faq/#what-happens-if-a-monitoring-agent-becomes-unavailable-how-can-i-ensure-my-mongodbs-are-always-monitored

Our doc's are incorrect about what triggers an "agent down" alert.

Currently we state:

The monitoring agent is fairly robust, and MMS automatically sends an Agent Down alert when a monitoring agent becomes unavailable. However, once you have completed your initial MMS setup, a second monitoring agent can be added. If one monitoring agent fails, the other can continue monitoring.

This is incorrect, as MMS Agent Down alerts will only be triggered when there are 0 of X agents detected as available for a given group. Not when any single agent is down.


Generated at Thu Feb 08 07:43:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.