[DOCS-12745] "Cluster is missing an active mongos" alert is possibly misleading Created: 22/May/19 Updated: 29/Oct/23 Resolved: 23/May/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Amit Jain | Assignee: | Steve Renaker (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Alerts, monitoring | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 4 years, 38 weeks ago |
| Description |
DescriptionIn the alerts documentation:
For the condition "Cluster is missing an active mongos", it says the alert trigger is "Ops Manager cannot reach a mongos for the cluster." At least one customer was misled into believe that to mean they would be alerted if a mongos router wasn't running. In fact, that alert will only fire if *all* mongoesses are down. Please if possible change the alert trigger description to
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Steve Renaker (Inactive) [ 23/May/19 ] |
| Comment by Githook User [ 23/May/19 ] |
|
Author: {'name': 'Steve Renaker', 'email': 'steve.renaker@mongodb.com', 'username': 'steveren'}Message: |