[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   

Description

In 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

Ops Manager cannot reach any of the mongos for the cluster.

 

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Steve Renaker (Inactive) [ 23/May/19 ]

PR: https://github.com/10gen/mms-docs/pull/2346

Comment by Githook User [ 23/May/19 ]

Author:

{'name': 'Steve Renaker', 'email': 'steve.renaker@mongodb.com', 'username': 'steveren'}

Message: DOCS-12745: 'Cluster is missing an active mongos' alert is possibly misleading (#2346)
Branch: master
https://github.com/10gen/mms-docs/commit/bccd22659474afceec69d2b048ad2077c6800a37

Generated at Thu Feb 08 08:05:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.