What is a one sentence summary of your feature request?
Ability to modify schedule or throttle windows server monitoring plans.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
I would like the ability to schedule when a monitoring plan runs, or have the ability to throttle how many servers are checked at a given time. Currently when a windows server monitoring plan kicks off, it creates a CPU storm on a VMware cluster hosting hundreds of servers. While the storm is short lived, its causing temporary issues with timeouts and unnecessary DRS migrations.
How do you currently solve the challenges you have by not having this feature?
Currently we have to monitor less servers than we would if we had the ability to throttle the check.
Thank you for the detailed write-up — this is a real concern, especially in large VMware environments.
A couple of things worth noting:
If you’re collecting remotely, there is already an option to limit the number of servers processed concurrently. I’d recommend reaching out to our Support team, who can help with configuration.
If you’re using the agent-based collection mode, the monitoring plan should not generate significant remote load on the hypervisor cluster in the first place, since data is collected locally on each host — so that approach may be worth considering if it fits your setup.
Either way, controlling collection concurrency is something that can be addressed today. Support will be best placed to advise on the right setting given your specific monitoring plan configuration.