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

Automatically pause a down sensor

Votes:

0

Is it possible to automatically pause a "down" sensor?

automatically custom-notification pause prtg sensor

Created on Mar 20, 2010 8:29:20 PM

Last change on Aug 12, 2010 8:15:36 AM by  Daniel Zobel [Product Manager]



Best Answer

Accepted Answer

Votes:

4

Dear Gerard,

this should actually be possible using a work-around with two notifications:

  • The first notification with a 'default' latency of for example 60s would be the 'normal' notification (email for instance).
  • The second notification should have a larger latency and would be a HTTP-Action notification towards PRTG itself, to pause the sensor using PRTGs API (using the new placeholder %sensorid you should be able to insert the ID automatically): Pause a sensor or object indefinitely: /api/pause.htm?id=%sensorid&action=0

Best Regards.

Created on Mar 22, 2010 3:18:04 PM by  Torsten Lindner [Paessler Support]

Last change on Jun 30, 2010 3:06:17 PM by  Daniel Zobel [Product Manager]



6 Replies

Votes:

-2

no, that is not possible. You could pause the sensor by dependency, meaning that the sensor would get paused if another sensor goes into an error state.

If a sensor would get paused (not being monitored any more) once it goes into an error state, how should the software notice when it is up and running again.

Created on Mar 22, 2010 9:07:52 AM by  Aurelio Lombardi [Paessler Support]



Votes:

0

The idea was that the sensor should send it's notification and then go into a paused state. This would prevent a particular jittering sensor to send notifications every xx minutes.

After the problem is solved, the sensor should then be manually resumed.

Created on Mar 22, 2010 2:54:13 PM



Accepted Answer

Votes:

4

Dear Gerard,

this should actually be possible using a work-around with two notifications:

  • The first notification with a 'default' latency of for example 60s would be the 'normal' notification (email for instance).
  • The second notification should have a larger latency and would be a HTTP-Action notification towards PRTG itself, to pause the sensor using PRTGs API (using the new placeholder %sensorid you should be able to insert the ID automatically): Pause a sensor or object indefinitely: /api/pause.htm?id=%sensorid&action=0

Best Regards.

Created on Mar 22, 2010 3:18:04 PM by  Torsten Lindner [Paessler Support]

Last change on Jun 30, 2010 3:06:17 PM by  Daniel Zobel [Product Manager]




Votes:

0

What would be the value to Pause a sensor indefinitely in this case. I am simply using insanely long duration to accomplish this. For example duration=1008000. Could you please give an example to pause the sensor indefinitely.

Created on Mar 14, 2015 11:56:01 PM



Votes:

0

To pause a sensor, please use

/api/pause.htm?id=objectid&pausemsg=yourmessage&action=0

To resume the sensor with an API call, please use

/api/pause.htm?id=objectid&pausemsg=yourmessage&action=1

Created on Mar 16, 2015 2:00:13 PM by  Arne Seifert [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.