We have a number of sensors on a schedule to not trigger overnight. At 9 am when they start up again, they all fire up within a short time of each other.
Many of these sensors involve querying a database, so we get a spike in database reads at 9 every morning.
Is there a way to spread out the re-activation of the sensors - say, turn on one-at-a-time over half an hour or an hour - to reduce the performance impact on our database?
Article Comments
Dear myprosperity,
Actually there is no way to stagger the sensors with a specific setting. PRTG automatically tries to spread the sensor scans over a certain time span to avoid flooding a target-host with a huge amount of requests. However, all these requests will be triggered in a very short time span if all these sensors use the same schedule.
Due to that, we recommend to set different schedules to the sensors (e.g. schedule-A for 20 sensors starts at 9am, schedule-B for 20 sensors starts at 9:30am, schedule-C for 20 sensors starts at 10am, etc).
To create/edit your individual schedules, please go to "Setup >> Account Settings >> Schedules".
Best regards,
Sven
Jan, 2017 - Permalink
Dear myprosperity,
Actually there is no way to stagger the sensors with a specific setting. PRTG automatically tries to spread the sensor scans over a certain time span to avoid flooding a target-host with a huge amount of requests. However, all these requests will be triggered in a very short time span if all these sensors use the same schedule.
Due to that, we recommend to set different schedules to the sensors (e.g. schedule-A for 20 sensors starts at 9am, schedule-B for 20 sensors starts at 9:30am, schedule-C for 20 sensors starts at 10am, etc).
To create/edit your individual schedules, please go to "Setup >> Account Settings >> Schedules".
Best regards,
Sven
Jan, 2017 - Permalink