[DOCS-12097] Steps to remove a cluster from Ops Manager monitoring have disappeared Created: 28/Sep/18  Updated: 29/Oct/23  Resolved: 19/Oct/18

Status: Closed
Project: Documentation
Component/s: Ops Manager
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mariano Escribano Assignee: Anthony Sansone (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.opsmanager.mongodb.com/v4.0/tutorial/unmanage-deployment/


Participants:
Days since reply: 4 years, 51 weeks ago
Epic Link: DOCSP-1743
Story Points: 0.1

 Description   

Description

The page here for OM 3.6 https://docs.opsmanager.mongodb.com/v3.6/tutorial/unmanage-deployment/ contains instructions to remove the cluster from automation, or remove it entirely (from monitoring as well). If we look at the 4.0 version here https://docs.opsmanager.mongodb.com/v4.0/tutorial/unmanage-deployment/, the steps to remove it from monitoring as well are gone.

We reference this page a lot for situations where a cluster needs to be removed entirely and re-added, so it would be nice to continue listing both options in the new page. Can we add it back?

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Githook User [ 20/Feb/19 ]

Author:

{'name': 'Anthony Sansone', 'username': 'atsansone', 'email': 'tony.sansone@mongodb.com'}

Message: (DOCS-12488): Backport DOCS-12097 to v4.0 - Restored monitoring after disabling automation.
Branch: v4.0
https://github.com/10gen/mms-docs/commit/00191473df472ec90b9c5394a67718a25a859f63

Comment by Githook User [ 19/Oct/18 ]

Author:

{'name': 'Anthony Sansone', 'email': 'tony.sansone@mongodb.com', 'username': 'atsansone'}

Message: (DOCS-12097): Restored monitoring after disabling automation.
Branch: master
https://github.com/10gen/mms-docs/commit/926c19ec07f4645c9902b28c1d58bf670ecd42f7

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