Votes:
I am trying to run a sensor test at 08:00 every 24 hours only to get the result of a specific query to a database table. I know the query works fine, but I just want to be able to run the query at a specific time of the day.
Last change on May 11, 2015 1:27:03 PM by
Votes:
This article applies as of PRTG 22
Sensors retrieve monitoring data in defined time spans called scanning intervals. PRTG comes with predefined scanning intervals that you can select in the sensor settings.
You can also set individual periods of time for sensor scans. For example, you can run a sensor every 30 seconds (30s), 15 minutes (15m), 12 hours (12h), and 24 hours (1d) by default. You can also define custom scanning intervals, like 20 minutes (20m) or 2 hours (2h). For more information, see PRTG Manual: Monitoring.
However, sometimes it can be convenient to run a sensor at certain points in time only. For example, you use an SQL sensor and want it to monitor your database only once a day at a given time, or you use an IMAP sensor to check your emails for successful backup messages that are delivered once a day at a particular time.
Follow these steps to define when you want a sensor to scan your network:
@ UTC hh:mm
For more points in time, write in one line:
@ UTC hh:mm , hh:mm
@ UTC hh:mm , hh:mm , hh:mm
@ UTC hh:mm , hh:mm , hh:mm , hh:mm
Notes:
Examples:
Note: Usually, sensor scans are executed at exactly the time you define here. If you encounter frequent divergences, your system might be overloaded. Keep in mind to set different points in time if you have many sensors that create a lot of workload together.
Note: The points in time for sensor scans are always based on the Coordinated Universal Time (UTC). Your local time may be different from the UTC: The PRTG web interface and reports use your local time.
If you set @ UTC points in time to define a scanning interval for a sensor, the live graph always regards your data as 24h-interval data (corresponding to the every 24 h interval), although you might have defined more than one scanning time per day.
This means that in a default 120 values live graph, you will see a horizontal axis that covers a time span of 120 days, at least at the beginning of your measurements. With your historic data base growing bigger, the horizontal axis adapts if you set your sensor to scan more often than once a day.
Created on May 11, 2015 4:14:33 PM by
Last change on Jan 4, 2023 9:56:26 AM by
25 Replies
Votes:
This is not possible at the moment, but we might make that available in the next version.
For now, you can set the sensor's scanning interval to 24 hours, but you cannot specify at which time of the day it will be run.
Created on Apr 13, 2010 5:01:32 AM by
Last change on Apr 13, 2010 7:46:19 AM by
Votes:
Another solution is to create a sensor that runs with an interval of one hour and limit the time that the sensor actually runs by using a schedule that allows only one specific hour.
Created on Apr 13, 2010 10:53:40 AM by
Votes:
This still has not been changed with the software but the solution from Dirk above can accommodate this necessity if it is only a work around.
Created on Aug 1, 2013 2:55:38 PM by
Votes:
We're taking a second look at this in 2015. But I cannot promise anything, I'm sorry.
Created on Oct 27, 2014 10:30:45 AM by
Votes:
Please bear with us a little longer. I expect such a feature to be released in the PRTG Canary release channel in the next months. Please watch this article for further information.
Created on Feb 6, 2015 8:05:33 AM by
Votes:
This article applies as of PRTG 22
Sensors retrieve monitoring data in defined time spans called scanning intervals. PRTG comes with predefined scanning intervals that you can select in the sensor settings.
You can also set individual periods of time for sensor scans. For example, you can run a sensor every 30 seconds (30s), 15 minutes (15m), 12 hours (12h), and 24 hours (1d) by default. You can also define custom scanning intervals, like 20 minutes (20m) or 2 hours (2h). For more information, see PRTG Manual: Monitoring.
However, sometimes it can be convenient to run a sensor at certain points in time only. For example, you use an SQL sensor and want it to monitor your database only once a day at a given time, or you use an IMAP sensor to check your emails for successful backup messages that are delivered once a day at a particular time.
Follow these steps to define when you want a sensor to scan your network:
@ UTC hh:mm
For more points in time, write in one line:
@ UTC hh:mm , hh:mm
@ UTC hh:mm , hh:mm , hh:mm
@ UTC hh:mm , hh:mm , hh:mm , hh:mm
Notes:
Examples:
Note: Usually, sensor scans are executed at exactly the time you define here. If you encounter frequent divergences, your system might be overloaded. Keep in mind to set different points in time if you have many sensors that create a lot of workload together.
Note: The points in time for sensor scans are always based on the Coordinated Universal Time (UTC). Your local time may be different from the UTC: The PRTG web interface and reports use your local time.
If you set @ UTC points in time to define a scanning interval for a sensor, the live graph always regards your data as 24h-interval data (corresponding to the every 24 h interval), although you might have defined more than one scanning time per day.
This means that in a default 120 values live graph, you will see a horizontal axis that covers a time span of 120 days, at least at the beginning of your measurements. With your historic data base growing bigger, the horizontal axis adapts if you set your sensor to scan more often than once a day.
Created on May 11, 2015 4:14:33 PM by
Last change on Jan 4, 2023 9:56:26 AM by
Votes:
Hi Frank,
We are still collecting some customer feedback, the more people requesting this feature, the higher the chance that it will be developed.
Best regards, Felix
Created on Sep 8, 2015 5:11:41 AM by
Votes:
@silvaric You should use a combination of schedules and custom scanning intervals. For example, if your VPN should be checked four times between 3pm and 4pm, you'll use the following:
Timeslot: @UTC 3:00,3:15,3:30,3:45,3:59
Schedule:
This will pause the sensor outside of those times, i.e. from 4pm to 3pm and you won't receive any notifications then.
Remember that the schedule uses the timezone of the server whilst the timeslots use UTC, so you need to fiddle a bit with the times.
@FVE That's a good idea, I'll bring it up to our documentation team :)
Created on Apr 25, 2017 8:41:17 AM by
Votes:
Hi there,
There are only two possibilities in this case. Either you leave it on UTC 0 and it will run on midnight the first half of the year and 1 AM on the other half or you change the scanning interval settings once a year to UTC 0 and +/-1 UTC.
Best regards.
Created on Dec 25, 2017 7:34:31 AM by
Votes:
Hi there,
Please note that they run in UTC, you might be located in a different timezone.
Best regards.
Created on Apr 30, 2018 7:09:37 AM by
Last change on Apr 30, 2018 7:09:51 AM by
Votes:
Hi there,
I am afraid that is not possible. The reason is to avoid false configurations which can lead to an overloaded PRTG installation.
Best regards.
Created on Jun 27, 2018 6:00:15 PM by
Add comment