[DOCS-10985] Regression: 3.4 Docs do not explain "healthy members" for alerting like 2.0 Docs Created: 06/Nov/17 Updated: 29/Oct/23 Resolved: 29/Aug/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Brian Blevins | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 5 years, 24 weeks ago |
| Epic Link: | DOCSP-1743 |
| Story Points: | 0.3 |
| Description |
|
The Ops Manager 2.0 documentation provides an explanation of what constitutes a healthy replica set member. https://docs.opsmanager.mongodb.com/v2.0/reference/alerts/#Number-of-Healthy-Members-is A replica set member is healthy if its state, as reported in the rs.status() output, is either PRIMARY or SECONDARY. Hidden secondaries and arbiters are not counted. However, this important information is missing from both the Ops Manager 3.4 documentation and the Cloud Manager documentation. I did not find any alternative location where this might have been moved. https://docs.opsmanager.mongodb.com/v3.4/reference/alerts/#replica-set-alerts https://docs.cloudmanager.mongodb.com/reference/alerts/#replica-set-alerts |
| Comments |
| Comment by Githook User [ 29/Aug/18 ] |
|
Author: {'name': 'Anthony Sansone', 'email': 'tony.sansone@mongodb.com', 'username': 'atsansone'}Message: ( |
| Comment by Githook User [ 29/Aug/18 ] |
|
Author: {'name': 'Anthony Sansone', 'email': 'tony.sansone@mongodb.com', 'username': 'atsansone'}Message: ( |
| Comment by Githook User [ 29/Aug/18 ] |
|
Author: {'name': 'Anthony Sansone', 'email': 'tony.sansone@mongodb.com', 'username': 'atsansone'}Message: ( |