PRTG Manual: Account Settings—Notification Templates

Template Name

Enter a meaningful name for the notification template, for example, SMS to service team.

Tags

Enter one or more tags. Confirm each tag with the space, comma, or enter key. You can use tags to group sensors and use tag-filtered views later on. Tags are not case sensitive. Tags will be automatically inherited.

Status

Select the status of the notification template. Choose between:

• Started: When the notification template is started or active, PRTG executes the notifications defined in the template whenever it is triggered.
• Paused: When the notification template is paused, PRTG does not execute any notification(s) defined in the template.

Schedule

Use schedules to activate a notification template only during specific time spans. This way you can pause notifications, for example, during regular maintenance periods or server reboots.

Select None, if you want your notification template to be always active (24/7). Choose one of the suggested schedules from the list to define a specific period for the notification template to be active.

The overall status of the notification template needs to be Started to apply any schedule settings.

To create your own schedules or to change existing schedules, see section Account Settings—Schedules.

Notification Handling During Paused Status

Define how PRTG handles notifications that are triggered while the notification template is set to Paused or during a scheduled pause.

• Collect notifications and send them when reactivated: PRTG collects all notifications that are triggered while the notification template is paused and sends them all out once the Paused status ends.
• Discard notifications during paused status: PRTG discards all notifications that are triggered while the notification is paused.

Method

Define if and how PRTG summarizes several notifications into one or more messages (max. 1,000 characters). Define if several notification triggers are to be collected over a specified time period and then sent as a single summarized notification. Choose from:

• Always notify ASAP, never summarize: Always send out one notification for each received notification trigger as soon as possible (for example, immediately).
• Send first DOWN message ASAP, then summarize: When receiving several DOWN triggers, send the first notification immediately, then keep summarizing notification triggers into one message, regardless of sensor status.
• Send first DOWN and UP message ASAP, then summarize: When receiving several DOWN or UP triggers, send each first notification immediately, then keep summarizing notification triggers into one message, regardless of sensor status.
• Send all DOWN messages ASAP, summarize the others: When receiving several DOWN triggers, send out one notification for each trigger received, but summarize notifications for all non-DOWN triggers into one message.
• Send all DOWN and UP messages ASAP, summarize the others: When receiving several DOWN or UP triggers, send out one notification for each trigger received, but summarize the notifications for all non-DOWN and non-UP triggers into one message.
• Always summarize notifications, regardless of type: When receiving several notification triggers, summarize notifications, regardless of the kind of trigger received. Please note, the maximum number of notifications (see below) still applies.

Regardless of the option you choose, PRTG never summarizes notifications of the types Send Slack Message, Send Microsoft Teams Message, Execute HTTP Action, Execute Program, and Assign Ticket because it always sends them immediately. The messages of all other notification types can be summarized.

'first DOWN' and 'first UP' messages refer to trigger condition and clear condition respectively. You can also define 'WARNING' or 'UNUSUAL' states as trigger conditions or even thresholds or other triggers notification summarizations. The condition clear triggers, if applicable, are defined in the respective trigger conditions as well. The triggers all qualify as "first DOWN" or "first UP" messages.

PRTG collects up to 25 single notifications for one summarization and will send out the message as soon as this number is reached (or when the gathering time has passed). If there are more than 25 notifications within the defined time span, you will receive more than one message with up to 25 entries each. For example, 74 collected notifications would result in 3 summarized messages with 25, 25, and 24 collected notifications.

Subject for Summarized Messages

Define a subject that PRTG will include when sending summarized notifications. You can use the placeholder %SUMMARYCOUNT for the number of messages that are summarized.

The subject you define is only used for Send Email and Amazon SNS messages.

Timespan for Summarizing Messages (in Minutes)

Define a time span in minutes to define how long PRTG collects notifications for summarization. Please enter an integer value.

If you enter a rather long time span, for example, 60 minutes, PRTG will collect notifications for one hour before sending them out summarized unless other features (see above) require an earlier message dispatch.

User Group Access

Define which user group(s) will have access to the object that you are editing. A table with user groups and rights is shown; it contains all user groups from your setup. For each user group, you can choose from the following access rights:

• Inherited: Use the settings of the parent object.
• None: Users in this group cannot see or edit the object. The object does not show up in lists.
• Read: Users in this group can see the object and review its settings.
• Write: Users in this group can see the object, as well as review and edit its settings. However, they cannot edit access rights settings.
• Full: Users in this group can see the object, as well as review and edit its settings as well as edit access rights.

You can create new user groups in the System Administration—User Groups settings.

This notification method uses notification contacts to deliver the messages. Please set up and check them for the desired user accounts in advance under Account Settings—Notification Contacts.

The three options for recipients below (user, user group, email address) work simultaneously. Because of this, you can define more than one user as recipient of this notification. PRTG sends the notification email to the active email contacts of the user you select, to the active email contacts of all members of the user group you select, and to all email addresses you enter into the Send to Email Address field.

Sender

Define which email address and sender name will appear in the FROM part of your email notifications. Choose between:

• Default: Use the default sender email and name as defined in the global Notification Delivery settings.
• Custom: Override the global sender email and name.

Sender Email Address

Enter an email address to use as sender of all email notifications. This field overrides the global setting from the Notification Delivery tab. The default value is the global sender email.

The email address must be allowed by the outgoing SMTP server defined in the Notification Delivery settings.

Sender Name

Enter a sender to use as sender of all email notifications. This field overrides the global setting from the Notification Delivery tab. The default value is the global sender name.

Send to User

Select a user of your PRTG installation to send the notification email to. PRTG sends this notification to each email contact of this user account. You can add and edit email contacts of a user in Account Settings—Notification Contacts. Choose None to not use this feature.

Send to User Group

Select a user group to send an email with the notification to all members of this group. PRTG sends this notification to the email contact of every group member. You can edit user groups under System Administration—User Groups and email contacts under Account Settings—Notification Contacts. Choose None to not use this feature.

If you select a user group and a specific member of this group as recipients, the user will only receive a single email. This also applies if you enter an individual email address below that is already defined as an email contact of the selected user.

If you define individual email addresses (see below), to a specific user (see above), and a user group, PRTG sends the message to the individual email addresses, to the individual user, as well as to the members of the selected user group. In all cases, PRTG sends one message with all recipients in the "To" field of the email.

Send to Email Address

Enter one or more recipient email addresses to which PRTG sends the notification email. If you enter more than one address, separate them with commas. Leave this field empty to send this notification only to the email contacts of the user or members of the user group you choose above.

We recommend that you use the options Send to User and/or Send to User Group instead because you can manage the notification contacts of users more easily this way.

Subject

Enter the subject of the email notification.

Several placeholders (variables) are used here by default: [%sitename] %device %name %status %down (%message)

Format

Define the kind of email that PRTG sends when the notification is triggered. Choose from:

• HTML: PRTG uses the default HTML email template for the message part of the email.
  Please use an email client that can show HTML emails, otherwise you cannot read emails from PRTG.
• Text: PRTG uses the default plain text email template for the message part of the email.
• Text with custom content: PRTG uses custom plain text for the message part of the email. You can enter your individual text below.

Custom Content

This field is only visible if you select the custom text option above. Enter the desired message for this email notification in plain text format. You can use placeholders here.

Priority

Define the priority that PRTG sets for the email. Most email clients can show this priority flag. Choose from:

• highest
• high
• normal
• low
• lowest

Push notifications only work with the apps PRTG for Android and PRTG for iOS. You have to activate push notifications in the settings of your app first. For details about the setup, see the Knowledge Base: How can I send push notifications with PRTG?

This notification method uses notification contacts to deliver the messages. Please set up and check them for the desired user accounts in advance under Account Settings—Notification Contacts.

The PRTG server needs to communicate on port 443 to the PRTG Cloud to send push notifications, which is https://api.prtgcloud.com:443 (the same as for the Cloud HTTP sensor, the Cloud Ping sensor, and support tickets).

The two options for recipients below (user, user group) work simultaneously. Because of this, you can define more than one user as recipient of this notification. PRTG sends the notification to the active push contacts of the user you select and to the active push contacts of all members of the user group you select.

Send to User

Select a user of your PRTG installation to send the push notification to. PRTG sends this notification to each push contact of this user account. You can edit push contacts of a user in Account Settings—Notification Contacts and add push contacts by activating push notifications in the Android or iOS app with this user. Choose None to not use this feature.

Send to User Group

Select a user group to send the push notification to all members of this group. PRTG sends this notification to each push contact of every member of this group. You can edit user groups under System Administration—User Groups and push contacts under Account Settings—Notification Contacts. Choose None to not use this feature.

If you select a user group and a specific member of this group as recipients at the same time, this user receives the text message only one time.

Message

Define the message. A message with information about the sensor status is already predefined. Several placeholders (variables) are used here: [%sitename] %device %name %status %down (%message)

You can change the message to your liking. To reset this field to its default value, enter a single star symbol * (and nothing else).

You have to set up this notification method in the System Administration—Notification Delivery settings first.

This notification method uses notification contacts to deliver the messages. Please set up and check them for the desired user accounts in advance under Account Settings—Notification Contacts.

The three options for recipients below (user, user group, email address) work simultaneously. Because of this, you can define more than one user as recipient of this notification. PRTG sends the notification to the active SMS contacts of the user you select, to the active SMS contacts of all members of the user group you select, and to every phone number you enter into the Send to Number field.

This notification method uses the central proxy settings that you define for your PRTG core server. For details, see System Administration—Core & Probes (section Proxy Configuration).

Send to User

Select a user of your PRTG installation to send the notification to. PRTG sends this notification to each SMS contact of this user account. You can add and edit SMS contacts of a user in Account Settings—Notification Contacts. Choose None to not use this feature.

Send to User Group

Select a user group to send a text message with the notification to all members of this group. PRTG sends this notification to each SMS contact of every member of this group. You can edit user groups under System Administration—User Groups and SMS contacts under Account Settings—Notification Contacts. Choose None to not use this feature.

If you select a user group and a specific member of this group as recipients at the same time, this user receives the text message only one time. This also counts if you enter an individual phone number below that is already defined as an SMS contact of the selected user.

Send to Number

Define the number to which PRTG sends the text message. The format depends on the SMS provider. Usually, you use a plus sign "+", followed by country code and number. For example, enter +1555012345.

Ensure the number format meets the requirements of your SMS provider or the hardware that you use in combination with an API call. Sometimes a preceded plus sign is not required. A wrong format may result in undelivered messages!

If you enter more than one number, separate them by comma. Leave this field empty to send this notification only to the SMS contacts of the user or members of the user group you choose above.

We recommend that you use the options Send to User and/or Send to User Group instead because you can manage the notification contacts of users more easily this way.

Message

Define the message. A message with information about the sensor status is already predefined. Several placeholders (variables) are used here: [%sitename] %device %name %status %down (%message)

You can change the message to your liking. To reset this field to its default value, enter a single star symbol * (and nothing else).

Regardless of the Notification Summarization method chosen above, PRTG sends notifications of the type Send Slack Message always as soon as possible (ASAP). They are never summarized.

URL of Slack Webhook

Enter the URL of the incoming webhook that you set up in your Slack workspace.

For more information, see the Knowledge Base: How do I create a webhook for the PRTG Notifications to Slack and Microsoft Teams?

Sender Name

Enter a sender name to use as sender of Slack notifications. This field overrides the sender that you may have defined in your Slack workspace.

Title

Enter the title of your Slack notification.

The following placeholders (variables) are used here by default: %device %name

Subtitle

Enter the subtitle of your Slack notification.

The following placeholder (variable) is used here: %message

Content

Choose between the following options to define the content of your Slack notification:

• Use default content: The notification message will include information about the Status, Last Scan, Last Value, Last Up, Coverage, Downtime, Priority, Probe, and Group.
• Define custom content: The notification message will include the pieces of information that you choose in the Content options (see next step).

Select Content

This field is only visible if you select the Define custom content option above.

Add a check mark in front of the piece of monitoring information that you want PRTG to include in your Slack notification. Remove the check mark in front of the items that you do not want to include.

Multiple choices are possible.

The following types of monitoring information are available:

• Name

• Host

• Status

• Last Scan

• Last Value

• Message

• Last Down

• Last Up

• Coverage

• Downtime

• Uptime

• Priority

• Probe

• Group

• Device

• Date and time

• Timezone

• Comments (probe)

• Comments (group)

• Comments (device)

• Comments (sensor)

• History

For more information on these types of monitoring information, please refer to the placeholders.

Regardless of the Notification Summarization method chosen above, PRTG sends notifications of the type Send Microsoft Teams Message always as soon as possible (ASAP). They are never summarized.

URL of the Teams Webhook

Enter the URL of the incoming webhook that you set up in your Microsoft Teams workspace.

For more information, see the Knowledge Base: How do I create a webhook for the PRTG Notifications to Slack and Microsoft Teams?

Title

Enter the title of your Microsoft Teams notification.

The following placeholders (variables) are used here by default: %device %name

Subtitle

Enter the subtitle of your Microsoft Teams notification.

The following placeholder (variable) is used here: %message

Content

Choose between the following options to define the content of your Microsoft Teams notification:

• Use default content: The notification message will include information about the Status, Last Scan, Last Value, Last Up, Coverage, Downtime, Priority, Probe, and Group.
• Define custom content: The notification message will include the pieces of information that you choose in the Content options (see next step).

Select Content

This field is only visible if you select the Define custom content option above.

Add a check mark in front of the piece of monitoring information that you want PRTG to include in your Microsoft Teams notification. Remove the check mark in front of the items that you do not want to include.

Multiple choices are possible.

The following types of monitoring information are available:

• Name

• Host

• Status

• Last Scan

• Last Value

• Message

• Last Down

• Last Up

• Coverage

• Downtime

• Uptime

• Priority

• Probe

• Group

• Device

• Date and time

• Timezone

• Comments (probe)

• Comments (group)

• Comments (device)

• Comments (sensor)

• History

For more information on these types of monitoring information, please refer to the placeholders.

This option is not available in PRTG hosted by Paessler.

Logfile

Define the logfile into which PRTG writes the message. Choose between:

• Application: Use the Windows application logfile in the event log.
• PRTG Network Monitor: Write messages to the PRTG Network Monitor logfile in the Windows event log.

Event Source

This setting is only relevant when using the Application logfile. Enter the source for the event. Usually, this is the name of the application.

Event Type

Select the type of the event. Choose from:

• Error
• Warning
• Information

Event Log Message

Define the message. A message with information about the sensor status is already predefined. Several placeholders (variables) are used here. You can change it to your liking. To reset this field to its default value, enter a single star symbol * (and nothing else).

This option is not available in PRTG hosted by Paessler.

Host/IP

Define the IP address or DNS name of the computer running the syslog server.

You can receive and analyze syslog messages with the Syslog Receiver sensor.

Syslog Port

Enter the port number on which syslog messages are sent. By default, this is port number 514.

Only User Datagram Protocol (UDP) is supported.

Facility

Define the facility information. There are several options available from the list.

Encoding

Define the encoding of the syslog message that PRTG sends to your syslog receiver. Choose between:

• ANSI
• UTF-8

Message

Define the message. A message with information about the sensor status is already predefined. Several placeholders (variables) are used here. You can change it to your liking. To reset this field to its default value, enter a single star symbol * (and nothing else).

Depending on the status of the sensor that triggers the syslog notification, PRTG sets the Severity level of the message automatically.

OK

Severity level: Notice (5)

Warning

Severity level: Warning (4)

Error

Severity level: Error (3)

For information about the OIDs that PRTG uses in the content of the SNMP traps, see the Knowledge Base: Is it possible to send SNMP traps using PRTG?

This option is not available in PRTG hosted by Paessler.

Host/IP

Define the IP address or DNS name of the computer running the trap receiver.

You can receive and analyze SNMP trap messages with the SNMP Trap Receiver sensor.

SNMP Port

Enter the port number on which trap messages are sent. By default, this is port number 162.

Community String

Enter the community string of the device. By default, this is set to public. Please enter a string or leave the field empty.

Specific Trap Code

Enter a code that can help you identify the purpose of the trap. Default value is 0. Please enter an integer value.

Message ID

Enter an ID that helps you identify the origin of the trap. Please enter an integer value. PRTG sends it on the OID 1.3.6.1.4.1.32446.1.1.1.

Message

Define the message. A message with information about the sensor status is already predefined. Several placeholders (variables) are used here. You can change it to your liking. To reset this field to its default value, enter a single star symbol * (and nothing else).

Agent IP

Define the IP address of the agent. Leave this field empty to use the IP address of your PRTG web server.

Regardless of the Notification Summarization method chosen above, PRTG sends notifications of the type Execute HTTP Action always as soon as possible (ASAP). They are never summarized.

This notification method uses the central proxy settings that you define for your PRTG core server. For details, see section System Administration—Core & Probes (section Proxy Configuration).

For more details, see section Custom Notifications. You can find ready-to-use custom notifications in the PRTG Script World, see below.

URL

Enter the URL to which PRTG sends the request.

HTTP notifications work with and without SSL.

SNI (Server Name Indication)

Select if PRTG will send the SNI extension to the TLS protocol along with the HTTP request. Choose between:

• Do not send SNI (default): PRTG will not send an SNI when executing the HTTP action.
• Send SNI: PRTG will send an SNI when calling the target URL. Specify the SNI below.

Virtual Host (SNI)

This field is only visible if you select the SNI option above. Enter the SNI name that your endpoint configuration requires. Usually, this is the Fully Qualified Domain Name (FQDN) of the virtual host.

HTTP Method

Choose the HTTP method that you want PRTG to use. Choose from:

• GET

• POST
• PUT

• PATCH

Payload

This field is only visible if you choose POST, PUT, or PATCH above.

Enter a payload here. The payload is the data that PRTG will transmit to the URL you have specified. You can use placeholders here. Line breaks are supported.

No XML or JSON is allowed here!

Only the content type application/x-www-form-urlencoded is supported.

Regardless of the Notification Summarization method chosen above, PRTG sends notifications of the type Execute Program always as soon as possible (ASAP). They are never summarized.

For more details, see section Custom Notifications. You can find ready-to-use custom notifications in the PRTG Script World, see below.

This option is not available in PRTG hosted by Paessler.

Program File

Select an executable file from the list. PRTG runs it every time the notification is triggered. In this list, you see the files that are in the corresponding /Notifications/EXE sub-directory of your PRTG core server system. To appear in this list, store the files as BAT, CMD, COM, EXE, PS1, or VBS.

To find this path, see section Data Storage.

In a cluster setup, copy your files to every cluster node installation manually. This makes sure PRTG can execute the notification even when the master node fails. If your custom notification executes an external program, install it on all cluster nodes as well.

Parameters

Enter parameters with which the program file will be started. You can use placeholders here. For example, if you use a batch file that contains a %1 variable, you can provide a value for this variable here.

You need to escape special characters and whitespaces in your parameters and surround them with double quotes. See section Escape Special Characters and Whitespaces in Parameters for details.

Domain or Computer Name

Enter a Windows authority if you want to use another security context for the program than the security context of the PRTG probe service.

Username

Enter the username for Windows access.

Password

Enter the password for Windows access.

Timeout

Enter a timeout in seconds. After this time has passed, PRTG stops the process if it has not terminated yet. Please enter an integer value.

AWS Access Key ID

Enter your access key as shown in your login area at aws.amazon.com. Please enter a string.

AWS Secret Access Key

Enter your secret access key as shown in your login area at aws.amazon.com. Please enter a string.

Location

Define the location of your Amazon service. Choose one of the shown locations:

• US East (Northern Virginia)
• US West (Ohio)
• US West (Northern California)
• US West (Oregon)
• Canada (Central)
• EU West (Ireland)
• EU Central (Frankfurt)
• EU (London)
• Asia Pacific (Singapore)
• Asia Pacific (Sydney)
• Asia Pacific (Seoul)
• Asia Pacific (Tokyo)
• Asia Pacific (Mumbai)
• South America (Sao Paulo)

ARN

Enter the Amazon resource name. Please enter a string.

Subject

Enter the subject of the message. Please enter a string.

The maximum length for the subject is 202 characters. Characters that exceed this number will be cut off.

Message

Define the message. A message with information about the sensor status is already predefined. Several placeholders (variables) are used here. You can change it to your liking. To reset this field to its default value, enter a single star symbol * (and nothing else).

The message part is only sent if you use email based notifications delivered by Amazon SNS. For SMS delivery, only the subject is sent while the message part is ignored because of SMS size restrictions.

Regardless of the Notification Summarization method chosen above, PRTG sends notifications of the type Assign Ticket always as soon as possible (ASAP). They are never summarized.

For details about the ticket system, see section Tickets.

Assign to User or User Group

Specify whether to assign the notification ticket to a user group or to a single user. Choose between:

• To User Group: Select a user group below to which PRTG assigns this ticket.
• To User: Select the dedicated user below to whom PRTG assigns this ticket.

User Group / User

Select the user or user group to which PRTG assigns the notification ticket.

Subject

Enter the subject of the ticket. Several placeholders (variables) are used here by default. You can change it to your liking.

Content

Define the message in the ticket. A message with information about the sensor status is already predefined. Several placeholders (variables) are used here. You may change it as you wish.

When Condition Clears

Specify if PRTG closes the ticket automatically when the defined trigger condition clears. Choose between:

• Close ticket automatically (recommended): PRTG closes the ticket automatically if the trigger condition is not met anymore.
• Leave ticket open: PRTG does not close the ticket after the condition has cleared.