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

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

Example of Notification Trigger Settings

Example of Notification Trigger Settings

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

PRTG already includes a default notification trigger for the root group. This default notification trigger initiates the standard notification Email and push notification to admin if there is any sensor in a 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 notification triggers show these notification triggers in section Triggers That Are Defined in Library Objects on the Notification Triggers tab.

Note

This section describes one of four steps to set up the notification system. To complete your notification setup, go through all of the following steps:

  1. Check and set up the Notification Delivery settings to define how and to which recipient PRTG sends messages.
    For more information, see section Notification Delivery.
  2. Check and set up Notification Contacts for users so that you can define them as recipients of notifications.
    For more information, see section Notification Contacts.
  3. Check and set up Notification Templates to define the notification methods and their content.
    For more information, see section Notification Templates.
    i_round_blueYou can also check or edit notification templates via the Notification Triggers tab. For more information, see section Sensor Notification Triggers Settings.
  4. Check and set up Notification Triggers for objects to define when notification messages are sent.
    For more information, see section Sensor Notification Triggers Settings.

i_round_blueWe 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 (because of an email server failure or other reasons), PRTG can still notify you via your smartphone. Set your latency setting to a state trigger and a notification via a different delivery method than the one for the first trigger. Or set up a second trigger with a different notification for the corresponding object.

i_square_cyanFor more information, see section Notifications.

Available Notification Triggers Settings

Open the Notification Triggers tab of an object to edit notification triggers. The available options are the same for all objects. When you define notification triggers for probes, groups, or devices, you can inherit them down to sensor level.

Triggers That Can Be Inherited from Parent Objects

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 notification triggers in probes, groups, or devices above the selected object in the object hierarchy. You can see the Type of notification trigger and the notification Rule that the monitoring object executes once this notification trigger is activated.

Setting

Description

Trigger Inheritance

Define the notification triggers that you want to use for the selected object:

  • Inherit all triggers from parent objects and use the triggers defined above: Use the triggers shown in the list of inherited triggers and use the specific triggers for this object defined above in section Notification Triggers. If the defined conditions are met, the corresponding triggers are activated and the notifications are initiated. To change settings of the specific notification triggers for this object, click b_trigger_edit to the right of it. To change settings of the inherited notification triggers, click the name of the monitoring object in the column Inherited from to open its Overview tab and then open the Notification Triggers tab.
  • Only use the triggers defined above: Do not use the inherited triggers shown in the list. Only use the triggers that you define for this object in section Notification Triggers.

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

Triggers That Are Defined in Library Objects

In section Triggers that are defined in library objects, you see all notification triggers that are set for libraries that contain the selected sensor.

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

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

i_round_blueYou cannot turn off trigger usage for the selected 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 Notification Triggers tab.

Trigger Types

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 triggers by forming sentences in "natural language". Different options are available for every type.

Add State Trigger

Define a trigger that is activated when a sensor changes its status. This is the most common reason to send out notifications. Hover over b_add and select Add State Trigger from the menu to add a new trigger, or click b_trigger_edit next to a trigger to change it. You can also directly edit notification templates. To do so, enable the check box next to a notification template and click b_multi_edit_settings.

Setting

Description

When sensor state is [...]

Select the status that triggers the notification:

  • Down: Trigger the notification if a sensor changes to the Down status.
  • Warning: Trigger the notification if a sensor changes to the Warning status.
  • Unusual: Trigger the notification if a sensor changes to the Unusual status.
  • Down (Partial): Trigger the notification if a sensor changes to the Down (Partial) status (available in a cluster).
  • Up: Trigger the notification if a sensor changes to the Up status.
  • Unknown: Trigger the notification if a sensor changes to the Unknown status.

...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 the Down status for only a few seconds. If the sensor status persists after the defined time in seconds, the notification is triggered. Enter an integer value.

i_round_redDo 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 [...]

Define the notification that PRTG sends out if the selected sensor status is true and the latency time defined has elapsed. Select a notification template. You see all notification templates defined under Setup | Account Settings | Notification Templates. Use the search box to filter for notification templates. You can also select no notification to only use other conditions for this trigger.

i_round_blueYou can also directly create and use new notification templates. Hover over b_add and click Add Notification Template.

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. Enter an integer value.

i_round_bluePRTG automatically takes the status from the first trigger condition above.

...perform [...]

Define the (second) notification that PRTG sends out if the selected sensor status is true and the escalation latency time defined has elapsed. Select a notification template. You see all notification templates defined under Setup | Account Settings | Notification Templates. Use the search box to filter for notification templates. You can also select no notification to only use other conditions for this trigger.

i_round_blueSelect a notification with a different delivery method than above to ensure the delivery in case technical issues with the first notification occur.

i_round_blueYou can also directly create and use new notification templates. Hover over b_add and click Add Notification Template.

...and repeat every [...] minutes

Define an interval in minutes in which PRTG repeatedly sends the escalation notification that you defined. Enter an integer value.

i_round_blueIf you enter 0, PRTG does not send repeating escalation notifications.

When sensor leaves [...] state after a notification was triggered, perform [...]

Define the a notification that PRTG sends out if the selected sensor status is not true anymore because the sensor status changed again. Select a notification template. You see all notification templates defined under Setup | Account Settings | Notification Templates. Use the search box to filter for notification templates. You can also select no notification to only use other conditions for this trigger.

i_round_bluePRTG sends notifications about cleared states if the time for the trigger activation elapsed (defined in the first line) and you select a notification template here. If you select no notification above, you get the notification about the cleared status nevertheless if you define it here. The definition of an "escalation" notification does not influence notifications for cleared conditions.

i_round_blueYou can also directly create and use new notification templates. Hover over b_add and click Add Notification Template.

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 monitored speed in a sensor changes (for example, a traffic sensor). Hover over b_add and select Add Speed Trigger from the menu to add a new trigger, or click b_trigger_edit next to a trigger to change it. You can also directly edit notification templates. To do so, enable the check box next to a notification template and click b_multi_edit_settings.

Setting

Description

When [...] channel

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 select a specific channel name from the list (there are different channels for every sensor). All following settings for this trigger are based on the chosen channel.

...is [...]

Select the condition that triggers the notification:

  • Above: Trigger the notification if the value of the selected channel exceeds a defined value.
  • Below: Trigger the notification if the value of the selected channel falls below a defined value.
  • Equal to: Trigger the notification if the value of the selected channel is the same as a defined value.
  • Not Equal to: Trigger the notification if the value of the selected channel is different than a defined value.

[value]

Define the value to which PRTG compares the channel data. Enter an integer value.

[scale]

Select the unit in which you entered the [value] above. [scale] and [time] together define the unit for the defined value. If the channel data is shown in a different unit, PRTG automatically converts values internally. Choose from:

  • bit
  • kbit
  • Mbit
  • Gbit
  • Tbit
  • Byte
  • KB
  • MB
  • GB
  • TB

[time]

Select the time for the scale (so you create a scale per time unit):

  • second
  • minute
  • hour
  • day

[scale] and [time] together define the unit for the defined value. If the channel data is shown in a different unit, PRTG automatically converts 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 only a few moments. If the combined channel condition of [value], [scale], and [time] persists after the defined time span, the notification is triggered. Enter an integer value.

i_round_redDo 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 [...]

Define the notification that is triggered if the combined channel condition of [value], [scale], and [time] is true and the latency time defined has elapsed. Select a notification template. You see all notification templates defined under Setup | Account Settings | Notification Templates. Use the search box to filter for notification templates. You can also select no notification to only use other conditions for this trigger.

i_round_blueYou can also directly create and use new notification templates. Hover over b_add and click Add Notification Template.

When condition clears after a notification was triggered, perform [...]

Define the 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. Select a notification template. You see all notifications defined under Setup | Account Settings | Notification Templates. You can also select no notification to only use other conditions for this trigger.

i_round_bluePRTG sends notifications about cleared conditions if the time for the trigger activation elapsed (defined in the first line) and you select a notification template here. If you select no notification above, you get the notification about the cleared condition nevertheless if you define it here.

i_round_blueYou can also directly create and use new notification templates. Hover over b_add and click Add Notification Template.

Save

Click Save to confirm your settings.

Cancel

Click Cancel to undo your changes.

i_round_blueNo 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. Hover over b_add and select Add Volume Trigger from the menu to add a new trigger, or click b_trigger_edit next to a trigger to change it. You can also directly edit notification templates. To do so, enable the check box next to a notification template and click b_multi_edit_settings.

Setting

Description

When [...] channel

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 select a specific channel name from the list (there are different channels for every sensor). 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. Enter an integer value.

[scale]

Select the unit in which you entered the [value] above. [scale] and [time] together define the unit for the defined value. If the channel data is shown in a different unit, PRTG automatically converts values internally. Choose from:

  • Byte
  • KB
  • MB
  • GB
  • TB

per [time],

Select the time for the scale (so you create a scale per time designation):

  • Hour
  • Day
  • Week
  • Month

[scale] and [time] together define the unit for the defined value. If the channel data is shown in a different unit, PRTG automatically converts values internally.

...perform [...]

Define the notification that is triggered if the [value] in the combined unit of [scale] and [time] is exceeded. Select a notification template. You see all notification templates defined under Setup | Account Settings | Notification Templates. Use the search box to filter for notification templates. You can also select no notification to only use other conditions for this trigger.

i_round_blueYou can also directly create and use new notification templates. Hover over b_add and click Add Notification Template.

Save

Click Save to confirm your settings.

Cancel

Click Cancel to undo your changes.

i_round_blueNo 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. Hover over b_add and select Add Threshold Trigger from the menu to add a new trigger, or click b_trigger_edit next to a trigger to change it. You can also directly edit notification templates. To do so, enable the check box next to a notification template and click b_multi_edit_settings.

Setting

Description

When [...] channel

Select the channel whose data PRTG considers for the comparison. Select Primary to generally use the primary channel of a sensor. You can define the primary channel in the sensor settings. Select a specific channel name from the list to apply the trigger to this channel. There are different channels for every sensor.

All following settings for this trigger are based on the chosen channel.

i_round_blueThe threshold trigger for a Total channel defined on device or group level or defined in libraries only applies to the sum channel of traffic sensors. This channel has ID -1. The trigger works with the Total channel of the following sensors:

  • Amazon CloudWatch EBS
  • IPFIX
  • IPFIX (Custom)
  • jFlow v5
  • jFlow v5 (Custom)
  • NetFlow v5
  • NetFlow v5 (Custom)
  • NetFlow v9
  • NetFlow v9 (Custom)
  • Packet Sniffer
  • sFlow
  • sFlow (Custom)
  • SMTP&IMAP Round Trip
  • SMTP&POP3 Round Trip
  • SNMP Traffic
  • Windows Network Card

...is [...]

Select the condition that triggers the notification:

  • Above: Trigger the notification if the value of the selected channel exceeds a defined value.
  • Below: Trigger the notification if the value of the selected channel falls below a defined value.
  • Equal to: Trigger the notification if the value of the selected channel is the same as a defined value.
  • Not Equal to: Trigger the notification if the value of the selected channel is different than a defined value.

[value]

Define the value PRTG compares the channel data to. Enter values in the smallest possible (base) unit, for example, in bytes, milliseconds, or percent. 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 only a few moments. If the defined channel condition persists after the defined time span, the notification is triggered. Enter an integer value.

i_round_redDo 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 [...]

Define the notification that is triggered if the defined channel condition is true and the latency time defined has elapsed. Select a notification template. You see all notification templates defined under Setup | Account Settings | Notification Templates. Use the search box to filter for notification templates. You can also select no notification to only use other conditions for this trigger.

i_round_blueYou can also directly create and use new notification templates. Hover over b_add and click Add Notification Template.

When condition clears after a notification was triggered, perform [...]

Define the notification that is triggered if the defined channel condition is not true anymore because the channel value has changed again. Select a notification template. You see all notification templates defined under Setup | Account Settings | Notification Templates. Use the search box to filter for notification templates. You can also select no notification to only use other conditions for this trigger.

i_round_bluePRTG sends notifications about cleared conditions if the time for the trigger activation elapsed (defined in the first line) and you select a notification template here. If you select no notification above, you get the notification about the cleared condition nevertheless if you define it here.

i_round_blueYou can also directly create and use new notification templates. Hover over b_add and click Add Notification Template.

Save

Click Save to confirm your settings.

Cancel

Click Cancel to undo your changes.

i_round_blueNo 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. Hover over b_add and select Add Change Trigger from the menu to add a new trigger, or click b_trigger_edit next to a trigger to change it. You can also directly edit notification templates. To do so, enable the check box next to a notification template and click b_multi_edit_settings.

Setting

Description

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 trigger is activated immediately whenever a sensor sends an 'on change' trigger. Select a notification template. You see all notification templates defined under Setup | Account Settings | Notification Templates. Use the search box to filter for notification templates.

i_round_blueYou can also directly create and use new notification templates. Hover over b_add and click Add Notification Template.

i_round_blueNo other options are available for this trigger type.

Object Settings Overview

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

Device and Sensor Setup