I want my SNMP Trap Receiver, Syslog Receiver or Event Log sensors to keep the error status, over more than one interval, even if the cause does not persist. How can I achieve this?
How can I configure sensors using speed limits to keep the status for more than one interval
3 Replies
This article applies to PRTG Network Monitor 16 or later
Using Triggers to Modify the Sensor's Status
Out of the box, PRTG will only change the sensor status for one single interval. If the next scan results in another status, the status will change accordingly.
There is a workaround which will apply to these sensor types:
- SNMP Trap Receiver Sensor
- Syslog Receiver Sensor
- WMI Event Log Sensor
- Event Log (Windows API) Sensor
Steps to Go
- Open the channel settings of
- the New Records channel of the Event Log sensors
- the Errors channel of the Syslog Receiver or Trap Receiver sensor
- Enter the value 0,00000001 into the Upper Error Limit (#/min) field. This will ensure, that the status will immediately change as soon as an alarm occurs and the limit is exceeded.
Note: This is the default setting for the Syslog and Trap Receiver sensors.
Full Size Image - This will set the sensor in down status as soon as a message that matches the sensor filter rules arrives. This will allow you to immediately trigger a notification.
- Click the Notifications tab of the sensor and choose these settings:
Full Size Image
This will immediately trigger a message and inform you about the issue.
Advanced Notes and Guides
We also want to provide you with information, which will allow you to display the Alarm status in PRTG until it's resolved. Therefore, follow these steps to setup the required API calls as well as the settings in PRTG:
- Create a device with a Green IT Sensor
Full Size Image - Create a new notification and choose Execute HTTP Action. This is where the PRTG API comes into play:
- Enter this code:
http(s)://YourServerIP/api/simulate.htm?id=objectid&action=1&username=YourUserAccount&Passhash=YourPasshash
- Note: You will find your passhash on the Setup | System Administration | User Accounts page for the respective user.
- Now you will be able to assign the correct object ID of the newly created Green IT sensor to the notification. This is fairly straight forward, just replace the objectid by the ID value shown on the Overview tab of your Green IT sensor.
- You can clear the simulated error status by right clicking the sensor's name and by clicking Resume
Result
Following this guide will allow you to quickly change the status of one sensor, based on a speed trigger or limit assigned to a particular sensor based on #/s results and to get a persistent overview of previews events.
See Also
Best regards, Felix
Created on Feb 14, 2017 9:28:41 PM by
Felix Saure [Paessler Support]
Last change on Jul 30, 2018 11:32:55 AM by
Brandy Mauff [Paessler Support]
totally lost in this manual. green IT sensor created for the new device, or can be on existing device? New notification means in setup under account settings? Where is objectid in 'just replace the objectid by the ID value shown on the Overview tab of your Green IT sensor.'? I can see ID in green IT sensor, but where to assign it??? Notification does not contain field named 'objectid'.
Hello Igoris,
The Green IT sensor can be added to the same device. If you then add a new notification and choose Execute HTTP Action, you can enter the ID into this webhook:
http(s):YourServerIP/api/simulate.htm?id=objectid&action=1&username=YourUserAccount&Passhash=YourPasshash
This can look like this if the ID of the sensor is 9000: http(s):YourServerIP/api/simulate.htm?id=9000&action=1&username=YourUserAccount&Passhash=YourPasshash
Does this help you creating this workaround?
Kind regards,
Felix Saure, Tech Support Team
Please log in or register to enter your reply.
Add comment