Hi Michel,
You can force a sensor to go into an error state by "simulating" an error
http://prtg.example.com/api/simulate.htm?id=1001&action=1&username=prtgadmin&password=prtgadmin
however any State Down notification triggers will simply report that the error was Simulated, rather than any actual error present on the sensor.
When designing notification trigger alerts, there are two variables you can play with: the scanning interval of the sensor, and (depending on the type of notification trigger used) the delay threshold.
For example, if you want a sensor to go red after 30 minutes, you could potentially have a scanning interval of 10 minutes, with an "If a Sensor Query Fails" of "Set sensor to warning for 2 intervals, then set to down". After 30 minutes of the sensor being in an error state, any notification triggers defined on the sensor would then be executed immediately. For State triggers, you can then of course an additional delay of when the actual notification should be sent out.
Using either method in isolation or combination ultimately allows you to achieve the same goal. Once you've identified the parameters you want to configure, you can then potentially batch apply these via the API.
Regards,
lordmilko
Add comment