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

How to force manual clearing of Alert




Sorry if this has been covered previously but I wasn't able to find an existing question covering this.

We have an SQL Query-based Sensor looking at a logging table for an in-house application. We have configured this sensor so that if a particular error message appears in the log table to raise an Alert (e.g. Sensor goes 'down'). The query uses the date-time so that it is only looking at the last hours worth of log entries.

My question is, how do I set PRTG so that when this Sensor goes 'down' it doesn't automatically come 'Up' at the end of the hour? Ideally what I am trying to achieve is have the Sensor go 'Down', generate an Alert and then have one of our technicians go and investigate that error before manually clearing it and allowing the Sensor to come 'Up'.

This is especially important if the error condition occurs during the night - as it currently is, the sensor comes up and therefore the alert is cleared before our technicians come to work in the morning so they don't even see that it was down. We tried using email alerting, but as we have so many sensors (other than this one), the emails get lost - especially when there is an 'up' email for that same sensor, it is easy to delete both emails thinking the problem was only intermittant and the problem has self-resolved. The other thing we tried was removing the 1-hour time period, but this means that if there is EVER an error entry, the sensor stays 'down' - although this does allow us to acknowledge the sensor and investigate, when we resolve the issue, the sensor still shows as 'down' (we definitely do not want to wipe that error entry from the log table).

Any ideas?



prtg sensor sql

Created on Jan 17, 2014 1:29:42 AM

1 Reply




The only way that I can think of to do something like this would be that when the sensor went into error status, you could make an API call with another notification that would put the sensor into a simulated error status, that way the sensor wouldn't come back up until someone clicked on the sensor and resumed it. Please note though that during the simulated error status, NO OTHER DATA will be collected for the sensor until it is resumed. You can find the API calls that you would need to use under Setup-> PRTG API.

Created on Jan 17, 2014 2:27:01 PM by  Greg Campion [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.