Content Previous Next

PRTG Manual: Sensor Notifications Settings

<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Sensor Notifications Settings

The status or the data of a sensor can trigger notifications. Using this mechanism, you can configure external alerting tailored to your needs.

Example of Notification Trigger Settings

Click here to enlarge: http://media.paessler.com/prtg-screenshots/notification_trigger.png

Although the sensors activate a trigger, you can set notification triggers higher in the hierarchy (for example for groups or devices). Because of this you can define triggers for multiple sensors using the inheritance mechanism. Monitoring objects with inherited triggers show these in section Triggers That Can Be Inherited From Parent Object(s) on the Notifications tab.

PRTG already includes a default notification trigger for the Root Group. This default trigger provokes the standard notification Email and push notification to admin if there is any sensor in down status in your PRTG installation for at least 10 minutes.

You can also define notification triggers in Libraries. Sensors that are in a library with defined triggers show these triggers in section Triggers That Are Defined in Library Object(s) on the Notifications tab.

Note

This section describes one of four steps to set up the notification system in PRTG. A complete notification setup involves:

Checking and setting up the Notification Delivery settings. This tells PRTG how and where to send messages.
For detailed information, see System Administration—Notification Delivery.
Checking and setting up Notification Contacts for the users of your PRTG installation. This defines where to send notifications.
For detailed information, see Account Settings—Notification Contacts.
Checking and setting up Notifications. This defines the kind of message and its content.
For detailed information, see Account Settings—Notifications.
Checking and setting up Notification Triggers for objects. This provokes the defined notifications.
For detailed information, see Sensor Notifications Settings.

We recommend that you always set up at least two notifications with different delivery methods for a notification trigger, for example, one email notification and one SMS notification. If delivery via email fails (due to an email server failure or other reasons), PRTG can still notify you via your smartphone. Simply set your latency setting to a state trigger and a notification via a delivery method other than the one for the first trigger. Or set up a second trigger with another notification for the corresponding object.

For background information, please see the Notifications section.

Available Notification Triggers Settings

On an object's detail page, open the Notifications tab to change sensor notification triggers. The available options are the same for all objects. When defining triggers for probes, groups, or devices, they can be inherited down to sensor level.

Triggers that can be inherited from parent object(s)
You see a list of all notification triggers that are defined higher in the hierarchy. The list is empty and shows the message (no triggers defined) when you have not set any triggers in probes, groups, or devices above the current object in the Object Hierarchy. You can see the Type of trigger and the Notifications that the monitoring object executes once this trigger is activated.
Trigger Inheritance	Define if you want to use the triggers shown above on the current object. Choose between: Inherit all triggers from parent objects and use the triggers defined below: Use the triggers shown above. If the defined condition is met, the corresponding trigger is activated and the notification provoked. Click the notification name to open its settings page. Click the name of the monitoring object in the column Inherited from to open its Overview tab. Only use triggers defined below: Do not use the triggers shown above. Only use the triggers that you define below in section Object Triggers for this object. This setting is valid for all triggers shown above. It is not possible to only select some of the triggers.

Triggers that can be inherited from parent object(s)

You see a list of all notification triggers that are defined higher in the hierarchy. The list is empty and shows the message (no triggers defined) when you have not set any triggers in probes, groups, or devices above the current object in the Object Hierarchy. You can see the Type of trigger and the Notifications that the monitoring object executes once this trigger is activated.

Trigger Inheritance

Define if you want to use the triggers shown above on the current object. Choose between:

Inherit all triggers from parent objects and use the triggers defined below: Use the triggers shown above. If the defined condition is met, the corresponding trigger is activated and the notification provoked. Click the notification name to open its settings page. Click the name of the monitoring object in the column Inherited from to open its Overview tab.
Only use triggers defined below: Do not use the triggers shown above. Only use the triggers that you define below in section Object Triggers for this object.

This setting is valid for all triggers shown above. It is not possible to only select some of the triggers.

In section Triggers that are defined in library object(s) you see all notification triggers that are set for Libraries that contain the currently selected sensor.

Triggers that Are Defined in Library Object(s)
You see a list of all notification triggers that are defined in libraries that include the currently selected sensor. The list is empty and shows the message (no triggers defined) when you have not set any triggers in libraries that contain the current sensor. You can see the Type of trigger and the Notifications that the sensor executes once this trigger is activated. Click the notification name to open its settings page. Click a library name in the column Inherited from to view this library. You cannot turn off trigger usage for the current sensor from a library here. If you do not want to use any notification triggers from a library for this sensor, open the library and remove this sensor from it or refine the triggers on the Notifications tab.

Triggers that Are Defined in Library Object(s)

You see a list of all notification triggers that are defined in libraries that include the currently selected sensor. The list is empty and shows the message (no triggers defined) when you have not set any triggers in libraries that contain the current sensor. You can see the Type of trigger and the Notifications that the sensor executes once this trigger is activated.

Click the notification name to open its settings page. Click a library name in the column Inherited from to view this library.

You cannot turn off trigger usage for the current sensor from a library here. If you do not want to use any notification triggers from a library for this sensor, open the library and remove this sensor from it or refine the triggers on the Notifications tab.

You can set up one or more of the following triggers, each with different setting options. Which trigger types are visible depends on the kind of object you edit:

You can create all notification triggers by forming sentences in "natural language". There are different options available for every type.

Add State Trigger

Define a trigger that is activated when a sensor changes its current status. This is the most common reason to send out notifications. Click the Add State Trigger button to add a new trigger, or click the Edit button next to an existing notification to change it. Define the settings as described below. Every trigger provokes one or more notification(s) to be executed.

State Trigger
When sensor state is [...]	Select the condition that will trigger the notification. The trigger will be activated when a sensor enters the selected status. Choose from the dropdown menu: Down: The trigger is activated if a sensor changes to a Down status. Warning: The trigger is activated if a sensor changes to a Warning status. Unusual: The trigger is activated if a sensor changes to an Unusual status. Partial Down: The trigger is activated if a sensor changes to a Down (Partial) status (available in a cluster configuration).
...for at least [...] seconds	Define how many seconds PRTG waits before it sends out a notification (latency). This can avoid false alarms if a sensor 'flickers' and, for example, changes to a down status for just a few seconds. If the selected condition (the sensor status) persists after the defined time in seconds, the notification is triggered. Please enter an integer value. Do not define a latency that is shorter than the scanning interval of a sensor that uses this trigger! The notification trigger might not work as expected in this case. .
...perform [...]	Select a notification that PRTG sends out if the selected condition (the sensor status) is true and the latency time defined has elapsed. Choose a notification from the dropdown menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification to only use other conditions for this trigger.
When sensor state is [...] for at least [...] seconds	Define an escalation latency in seconds. This "escalation" triggers a second notification if the number of seconds you enter here has passed since the sensor status has entered the defined condition. Use this to automatically escalate a notification in case a problem persists for a longer time. Please enter an integer value. PRTG automatically takes the status from the first trigger condition above.
...perform [...]	Select a (second) notification that PRTG sends out if the selected condition (the sensor status) is true and the escalation latency time defined has elapsed. Choose a notification from the dropdown menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification to only use other conditions for this trigger. Select a notification with another delivery method than above to ensure the delivery in case of technical issues with the first notification.
...and repeat every [...] minutes	Define an interval in minutes in which PRTG sends the escalation notification (defined above) repeatedly. The second (escalation) notification defined will be resent every x minutes that you enter here. Please enter an integer value. If you enter 0, PRTG will not send repeating escalation notifications.
When condition clears after a notification was triggered perform [...]	Select a notification that PRTG sends out if the selected condition (the sensor status) is not true anymore because the sensor status changed again. Choose a notification from the dropdown menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification to only use other conditions for this trigger. PRTG sends notifications about cleared conditions if the time for the trigger activation elapsed (defined in the first line) and you choose a notification here. If you select no notification above, you will get the notification about the cleared condition nevertheless if you define it here. The definition of an "escalation" notification does not influence notifications for cleared conditions.
Save	Click Save to confirm your settings.
Cancel	Click Cancel to undo your changes.

Add Speed Trigger

Define a trigger that is activated when the currently monitored speed in a sensor changes (for example, a traffic sensor). Click the Add Speed Trigger button to add a new trigger, or click the Edit button next to an existing notification to change it. Define the settings as described below. Every trigger provokes one or more notification(s) to be executed.

Speed Trigger
When [...] channel	From the dropdown menu, select the channel whose data PRTG considers for speed comparison. Select Primary to generally use the primary channel of a sensor (you can define this in the sensor settings), or choose a specific channel name from the list (there are different channels for every sensor type). All following settings for this trigger are based on the chosen channel.
...is [...]	Select the condition that will trigger the notification. Choose from the dropdown menu: Above: The trigger is activated if the value of the selected channel exceeds a defined value. Below: The trigger is activated if the value of the selected channel falls below a defined value. Equal to: The trigger is activated if the value of the selected channel is the same as a defined value. Not Equal to: The trigger is activated if the value of the selected channel is different than a defined value.
[value]	Define the value to which PRTG compares the channel data. Please enter an integer value.
[scale]	From the dropdown menu, select the unit in which you entered the [value] above. [scale] and [time] together define the unit for the given value. If the channel data is shown in a different unit, PRTG will automatically convert values internally. Choose from: bit kbit Mbit Gbit Tbit Byte KByte MByte GByte TByte
[time]	Select the time for the scale (so you create a scale per time unit). Choose from the dropdown menu: second minute hour day [scale] and [time] together define the unit for the given value. If the channel data is shown in a different unit PRTG will automatically convert values internally.
..for at least [...] seconds	Define how many seconds PRTG waits before it sends out a notification (latency). This can avoid false alarms if a channel reaches a limit for just a few moments. If the combined channel condition of [value], [scale], and [time] persists after the defined time span, the notification will be triggered. Please enter an integer value. Do not define a latency that is shorter than the scanning interval of a sensor that uses this trigger! The notification trigger might not work as expected in this case.
...perform [...]	Select a notification that is triggered if the combined channel condition of [value], [scale], and [time] is true and the latency time defined has elapsed. Choose a notification from the dropdown menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification to only use other conditions for this trigger.
When condition clears perform [...]	Select a notification that is triggered if the combined channel condition of [value], [scale], and [time] is not true anymore because the channel value has changed again. Choose a notification from the dropdown menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification to only use other conditions for this trigger. PRTG sends notifications about cleared conditions if the time for the trigger activation elapsed (defined in the first line) and you choose a notification here. If you select no notification above, you will get the notification about the cleared condition nevertheless if you define it here.
Save	Click Save to confirm your settings.
Cancel	Click Cancel to undo your changes.

No escalation notification and no repeat are available for this trigger type.

Add Volume Trigger

Define a trigger that is activated when a sensor (for example, a traffic sensor) reaches a certain volume limit in a specified time. Click the Add Volume Trigger button to add a new trigger, or click the Edit button next to an existing notification to change it. Define the settings as described below. Every trigger provokes one or more notification(s) to be executed.

Volume Trigger
When [...] channel	From the dropdown menu, select the channel whose data PRTG considers for this comparison. Select Primary to generally use the primary channel of a sensor (you can define this in the sensor settings), or choose a specific channel name from the list (there are different channels for every sensor type). All following settings for this trigger are based on the chosen channel.
...has reached [value]	Define the value to which PRTG compares the channel data. If the channel data exceeds this value, a notification is triggered. Please enter an integer value.
[scale]	From the dropdown menu, select the unit in which you entered the [value] above. [scale] and [time] together define the unit for the given value. If the channel data is shown in a different unit, PRTG will automatically convert values internally. Choose between: Byte KByte MByte GByte TByte
per [time]	Select the time for the scale (so you create a scale per time designation). Choose from the dropdown menu: Hour Day Week Month [scale] and [time] together define the unit for the given value. If the channel data is shown in a different unit, PRTG will automatically convert values internally.
...perform [...]	Select a notification that is triggered if the [value] in the combined unit of [scale] and [time] is exceeded. Choose a notification from the dropdown menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification to only use other conditions for this trigger.
Save	Click Save to confirm your settings.
Cancel	Click Cancel to undo your changes.

No escalation notification, no repeat, and no notification when condition clears are available for this trigger type.

Add Threshold Trigger

Define a trigger that is activated when a sensor reaches specific values. Click the Add Threshold Trigger button to add a new trigger, or click the Edit button next to an existing notification to change it. Define the settings as described below. Every trigger provokes one or more notification(s) to be executed.

Threshold Trigger
When [...] channel	From the dropdown menu, select the channel whose data PRTG considers for this comparison. Select Primary to generally use the primary channel of a sensor (you can define this in the sensor settings), or choose a specific channel name from the list (there are different channels for every sensor type). All following settings for this trigger are based on the chosen channel.
...is [...]	Select the condition that will trigger the notification. Choose from the dropdown menu: Above: The trigger is activated if the value of the selected channel exceeds a defined value. Below: The trigger is activated if the value of the selected channel falls below a defined value. Equal to: The trigger is activated if the value of the selected channel is the same as a defined value. Not Equal to: The trigger is activated if the value of the selected channel is different than a defined value.
[value]	Define the value PRTG will compare the channel data to. Enter values in the smallest possible (base) unit, for example, in bytes, milliseconds, or percent. Please enter an integer value.
..for at least [...] seconds	Define how many seconds PRTG waits before it sends out a notification (latency). This can avoid false alarms in case a channel reaches a limit for just a few moments. If the defined channel condition persists after the defined time span, the notification is triggered. Please enter an integer value. Do not define a latency that is shorter than the scanning interval of a sensor that uses this trigger! The notification trigger might not work as expected in this case.
...perform [...]	Select a notification that is triggered if the defined channel condition is true and the latency time defined has elapsed. Choose a notification from the dropdown menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification to only use other conditions for this trigger.
When condition clears perform [...]	Select a notification that is triggered if the defined channel condition is not true any more because the channel value has changed again. Choose a notification from the dropdown menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification to only use other conditions for this trigger. PRTG sends notifications about cleared conditions if the time for the trigger activation elapsed (defined in the first line) and you choose a notification here. If you select no notification above, you will get the notification about the cleared condition nevertheless if you define it here.
Save	Click Save button to confirm your settings.
Cancel	Click Cancel to undo your changes.

No escalation notification and no repeat are available for this trigger type.

Add Change Trigger

Define a trigger that is activated by an 'on change' trigger. Some sensors offer the option to send such a trigger whenever sensor values have changed. Click the Add Change Trigger button to add a new trigger, or click the Edit button next to an existing notification to change it. Then define settings as described below. Every trigger will provoke one or more notification(s) to be executed.

Change Trigger
When sensor changes perform [...]	Select a notification that is triggered whenever a compatible sensor sends a 'change notification'. You can enable this option in the settings of some sensors. The notification trigger is activated immediately whenever a sensor sends an 'on change' trigger. Choose a notification from the dropdown menu. The menu shows all notifications defined in the Account Settings—Notifications settings.

There are no other options available for this trigger type.

Sensor Settings Overview

For information about sensor settings, please see the following sections:

Object Settings Overview

For more general information about object settings, please see section Object Settings.

Ajax Web Interface—Device and Sensor Setup—Topics

Other Ajax Web Interface Sections