What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Scanning Interval

Votes:

0

We have a custom sensor with a scanning interval set to @ UTC 07:10, 15:10, 23:10

However it runs at a higher frequency causing unwanted triggers when the query fails. There is no inheritance set but it acts like there is

Example

Date Time Execution Time Value Downtime Coverage

Averages 22,008 msec 66 # 35% 100%

Date Time  Execution Time  Value  Downtime  Coverage  14/03/2018 07:10 12,473 msec 100 # 0% 100% 13/03/2018 23:10 11,862 msec 100 # 0% 100% 13/03/2018 17:21 2,965 msec 100 # 0% 100% 13/03/2018 16:44 1,903 msec 1 # 100% 100% 13/03/2018 16:44 1,746 msec 1 # 100% 100% 13/03/2018 16:44 1,622 msec 1 # 100% 100% 13/03/2018 16:44 2,636 msec 1 # 100% 100% 13/03/2018 16:32 1,606 msec 1 # 100% 100% 13/03/2018 16:32 2,481 msec 1 # 100% 100% 13/03/2018 16:32 1,570 msec 1 # 100% 100% 13/03/2018 16:28 Error Error 100% 100% 13/03/2018 16:22 Error Error 100% 100% 13/03/2018 16:21 Error Error 100% 100% 13/03/2018 15:11 39,031 msec 100 # 0% 100% 13/03/2018 15:11 Error Error 100% 100% 13/03/2018 07:11 27,518 msec 100 # 0% 100% 13/03/2018 07:11 Error Error 100% 100% 12/03/2018 23:10 51,401 msec 100 # 0% 100% 12/03/2018 15:13 38,816 msec 100 # 0% 100% 12/03/2018 14:46 25,053 msec 1 # 100% 100% 12/03/2018 13:17 27,876 msec 1 # 100% 100% 12/03/2018 12:17 30,061 msec 1 # 100% 100% 12/03/2018 08:16 23,990 msec 1 # 100% 100% 12/03/2018 07:10 47,657 msec 1 # 0% 100% 11/03/2018 23:10 46,862 msec 100 # 0% 100% 09/03/2018 15:19 5,553 msec 100 # 0% 100% 09/03/2018 15:16 5,684 msec 1 # 100% 100% 09/03/2018 15:10 12,853 msec 1 # 100% 100% 09/03/2018 15:10 13,628 msec 1 # 100% 100% 09/03/2018 15:04 11,218 msec 1 # 0% 100% 09/03/2018 15:01 5,834 msec 100 # 0% 100% 09/03/2018 14:50 7,783 msec 1 # 100% 100% 09/03/2018 14:50 11,492 msec 1 # 100% 100% 09/03/2018 14:44 6,814 msec 1 # 100% 100% 09/03/2018 14:10 7,587 msec 1 # 100% 100% 09/03/2018 13:44 5,623 msec 1 # 100% 100% 09/03/2018 13:03 4,234 msec 1 # 100% 100% 09/03/2018 11:36 1,903 msec 1 # 100% 100% 09/03/2018 11:27 9,908 msec 1 # 100% 100% 09/03/2018 11:24 6,049 msec 1 # 0% 100% 09/03/2018 11:24 Error Error 100% 100%

custom-sensor scanning-interval sensor

Created on Mar 14, 2018 9:37:58 AM



3 Replies

Votes:

0

Hello there,

Thanks for your inquiry, we appreciate your contact regarding the matter!

To understand your configuration right, your Sensor is paused in the night by a schedule until 7:10 and then running in an 8 h scanning interval. Am I right? If not, please explain this in more detail for me. You can also send screenshots to [email protected]. Please use a subject that includes the ticket number PAE1009678.

In the table you sent, it seems that some scans are running due to a manual "check now".

Kind regards,
Birk Guttmann, Tech Support Team

Created on Mar 14, 2018 3:06:52 PM by Birk Guttmann [Paessler Support]



Votes:

0

Hi..

We don't manually run the scans but just rely on the interval of three times a day as you have said. That's all we expect to see assuming the scanning interval setting with PRTG does the scheduling internally. The script has no schedule component.

We don't do any "manual check now" - the data is from the sensors metrics

Alex

Created on Mar 15, 2018 1:59:03 PM



Votes:

0

Hi Alex,

A sensor is only running a scan before its interval when the following happens:
- someone runs a check now on one of the corresponding objects (Root, Probe, Group, Device, Sensors)
- The Probe connection got interrupted
- The sensor gets paused. This can happen due to inheritance, schedules, maintenance windows or manual pauses

If "check now" was executed by a user, you can see this in the current web server logs (default path: C:\ProgramData\Paessler\PRTG Network Monitor\Logs (Web Server)). Search here for the corresponding sensor ID. This is displayed in the upper right area of the sensor overview.

I would recommend to change the schedule, that the Senor is not running between the intervals, to prevent false alarms.

Kind regards,
Birk Guttmann, Tech Support Team

Created on Mar 16, 2018 12:04:00 PM by Birk Guttmann [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.