[DOCS-13835] [OM] Explain expected behavior after OM AppDB monitoring Enabled Created: 14/Aug/20 Updated: 08/Nov/23 |
|
| Status: | Backlog |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Diancheng Hu | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | request | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 3 years, 25 weeks, 5 days ago | ||||
| Story Points: | 2 | ||||
| Description |
DescriptionThe current docs page did not mention what functionalities will be disabled if OM AppDB monitoring Enabled. https://docs.opsmanager.mongodb.com/current/tutorial/enable-appdb-monitoring/ Might cause confusion. See conversation: https://mongodb.slack.com/archives/C1WJ164MU/p1597392943117000 Related PR: https://github.com/10gen/mms/pull/32222 We would like to add a "Learn More" link to the screen on the above PR once the documentation is updated.
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |