I've installed the Veeam MP 6.0 a few days ago and linked it with our SCOM 2012 SP1 environment (It' really something magically happening
Now after some time testing it I came to a point where I wanted to not get all the objects (datastores/resourcepools/vm's/vmfolders) in the SCOM monitoring.
This because some vm's are not cirtical/testing/dev/staging/... at the moment the only supported solution is to create a group in scom and make some dynamic rules to add the unnecessary objects to this group and disable the rules/monitors for this specific group with a bunch of overrides. (way to complex & causing way to much overhead)
Another unsupported solution was limiting the access of the readonly account on our VI but this also doens't seems to be the way to go.
Guess you know where my goal is?
There must be a much easier function in the nworks/veeammp back-ends.
If SCOM doesn't need all the object in the VI filter them not at the end but as close as possible to the VI to limit overhead & unnecessary resources get spoiled.
In VeeamONE there is a simple but very effective feature in the business view which solves this issue for our environment and for most of other environments i guess.
Just add some rules:
- do not monitor every vm which starts with "DEV"
- do not monitor apppools which equals to "Staging"
- do not monitor folder & descendant object "test vm's"
This is really a missing feature since it's already implemented in VeeamONE and we know you guys can get it done.
The collectors aren't lightweight machines when you monitor a decent VI environment, in our case we can filter out a few hundred vm's and a few datastores.
This really could safe us resources, effort and increase our flexibility which I guess you could only admit.
I've also discussed this with Mike Resseler from the Veeam team and he could only admit my concerns.
There are a few old & some very old discussions which also indicates this missing feature so maybe i'ts time to give it a try
Hope there will soon be an update with this feature included.