AdvisorAdvisorThanks a lot for the feedback & ideas @Mike Moniz & @Stuart Weenig!
We really enjoyed Mike suggestion of doing a script to actually poll the data in bulk - per device (instead of 1 query per service/process instance).
After reading some documentation & understanding how to use WMI on groovy (with help of some OutOfBox datasources) we ended up by rebuilding those 2 datasources (services & processes) using groovy (making use of the WMI class).
They're collecting exactly the same metrics as the out of the box ones & after 2/3 hours in production those really reduced the collector CPU/Memory usage - used 1 of our clients as a pilot
Previously the usage was constantly at >98%, now it's monitoring the same amount of services/processes & using 60-70% of CPU.
It increased the groovy instances exponentially - examples below
However, this doesn't seem to affect the collector resources usage that much.
We're also no longer seeing the WMI timeouts on the WMI instance runs. We guess this is really making a difference.
I know it's too soon to say this solved it, but by judging how the resource usage looks, this seems to make a big difference.
Also, the list of services changes, that's why we ended up using a property.
I'll share both datasources with you guys in a few minutes (I'll just attach the .XML file(s) to this thread) in case this is useful for anyone.
Regards,
