-
- Lurker
- Posts: 2
- Liked: never
- Joined: Dec 17, 2012 9:59 pm
- Full Name: Ev Moreno
- Contact:
nworks VMGUEST Unmonitored Group
Hi all, wondering if I can add vmguests into the unmonitored group to disable monitoring & alerting. P.s would also be good if someone could post the XML version of the MP as would like to understand the contents - if this not too rude. thanks. Evelyn
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Dec 17, 2012 9:59 pm
- Full Name: Ev Moreno
- Contact:
Re: nworks VMGUEST Unmonitored Group
Ignore request for mp contents used mpviewer. Still curious on how the unmonitored group works.
-
- VP, Product Management
- Posts: 1497
- Liked: 384 times
- Joined: Jan 01, 2006 1:01 am
- Contact:
Re: nworks VMGUEST Unmonitored Group
Hi Evelyn,
The VM Guest Unmonitored group is used internally by the MP, to disable workflows during certain discovery processes. This group disables some workflows for VMs while our discovery process is going on, so that these workflows don't try to run on the RMS, which could cause some errors.
The group is part of our sealed MP, so you can't modify it - there's no need anyway, because VMs automatically join and leave the group, controlled by our discoveries.
I agree - this group could be useful if you could add/remove VMs manually, and so disable alerting and data collection per-VM. (similar to Ops Mgr maintenance mode, but actually this group disables ALL data collection, not just alerting).
We could include an unsealed MP in our Resource Kit that would give you a copy of this group, for your own use. Then you could add and remove your own VMs as needed. Let me know if that would work for you!
Cheers
Alec
The VM Guest Unmonitored group is used internally by the MP, to disable workflows during certain discovery processes. This group disables some workflows for VMs while our discovery process is going on, so that these workflows don't try to run on the RMS, which could cause some errors.
The group is part of our sealed MP, so you can't modify it - there's no need anyway, because VMs automatically join and leave the group, controlled by our discoveries.
I agree - this group could be useful if you could add/remove VMs manually, and so disable alerting and data collection per-VM. (similar to Ops Mgr maintenance mode, but actually this group disables ALL data collection, not just alerting).
We could include an unsealed MP in our Resource Kit that would give you a copy of this group, for your own use. Then you could add and remove your own VMs as needed. Let me know if that would work for you!
Cheers
Alec
Who is online
Users browsing this forum: No registered users and 2 guests