Back using Solarwinds after a few years. I see a lot of improvements in 2019.04 but this one is wrecking my head. We are monitoring a VMware estate with the NPM agent and VMM. A common scenario:
- The C: drive space passes a threshold that triggers and alert
- The OS admin increases the raw disk size in vmware then extends the volume in the OS layer
- NPM now shows a new disk with the new size and another disk with the old size! They have different serial numbers!
This now keeps triggering alerts against a now ghost disk size This seems increbilty poor design if this is indeed a default aspect of the product still.
Questions:
- Is this designed behavior?
- If so why does the extended dis show a new serial number?
- If so, does this article still show the best way to resolve?
- Can I get around this using VMM to monitor or the like?
Thanks in advance guys.