PRTG Manual: Notification Delivery

On the Notification Delivery tab, you can define and test global settings for notification delivery. If you do not want to use a specific notification method, leave the respective fields empty.

i_round_blueThis documentation refers to an administrator that accesses the PRTG web interface on a master node. Other user accounts, interfaces, or failover nodes might not have all of the options in the way described here. In a cluster, note that failover nodes are read-only by default.

i_podIf 15 minutes (900) seconds have passed since your last credential-based login and you open a setup page from a different setup page, PRTG asks you to enter your credentials again for security reasons. A dialog box appears. Enter your Login Name and Password and click OK to continue.

In this section:

Note

You have to take the following four steps to set up and use notifications:

  1. Check and set up the notification delivery settings if you use PRTG Network Monitor. These settings define how PRTG sends messages.
  2. Check and set up notification contacts for the user accounts. These contacts define the recipients to which PRTG sends notifications.
  3. Check and set up several notification templates. These templates define the notification methods and their content.
    i_round_blueYou can also check or edit notification templates via the Notification Triggers tab. For more information, see section Notification Triggers Settings.
  4. Check and set up notification triggers settings for objects. These triggers define when PRTG sends notifications.

i_round_blueUsually, there are three successive attempts to deliver a notification. If all of these attempts fail, the notification is lost. To never miss a notification, we recommend that you always set up at least two notifications with different notification methods for a notification trigger, for example, one email notification and one SMS notification. If delivery via email fails, PRTG can still notify you via smartphone as a fallback. For example, use the latency setting of a state trigger to choose a notification with a different notification method than in the first trigger condition, or set up a second trigger with a different notification method for the corresponding object.

i_square_cyanFor a detailed step-by-step guide, see the Knowledge Base: How to set up notifications via the PRTG web interface.

i_square_cyanCustom notification scripts are also available in the PRTG Sensor Hub.

SMTP Delivery

SMTP Delivery

SMTP Delivery

Setting

Description

Delivery Mechanism

Define how PRTG sends emails via the Simple Mail Transfer Protocol (SMTP):

  • Use direct delivery with the built-in email server (default): Use the built-in SMTP relay server. This server manages its own email queue. For each email, it looks up the target SMTP server via the MX record of the target domain, and sends the email.
  • Use one SMTP relay server (recommended in LANs/NATs): Set up your own SMTP relay server to send emails. Enter data below.
  • Use two SMTP relay servers (primary and fallback server): Set up two SMTP relay servers with one as the primary relay server and one as the fallback relay server. Enter data below.

i_round_blueIf you monitor the IT infrastructure in your network address translation (NAT) or LAN, use your own LAN-based relay server to ensure faster delivery of notification emails.

i_podThis option is not available in PRTG Hosted Monitor. PRTG Hosted Monitor uses SendGrid for email notifications. For more information, see the Paessler website: FAQ – PRTG Hosted Monitor.

Sender Email Address

Enter an email address to use as the sender of all email notifications. This setting is global and applies to all email notifications by default.

i_round_blueYou can override the sender email in the settings of individual notification templates.

Sender Name

Enter a name to use as the sender of all email notifications. This setting is global and applies to all email notifications by default.

i_round_blueYou can override the sender name in the settings of individual notification templates.

i_round_blueIf the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?

HELO Ident

Enter a server name for the HELO part of the mail protocol.

i_round_blueFor some mail servers, the HELO identifier must be the valid principal host domain name for the client host. For more information, see SMTP RFC 2821.

i_round_redThe HELO identifier must be a unique name.

i_round_redOnly ASCII characters are allowed.

i_round_blueWe recommend that you use the Domain Name System (DNS) name of the PRTG core server system.

i_podThis option is not available in PRTG Hosted Monitor.

SMTP Relay Server

This setting is only visible if you select Use SMTP relay server (recommended in LANs/NATs) or Use two SMTP relay servers (primary and fallback server) above. Enter the IP address or DNS name of the SMTP relay server.

i_podThis option is not available in PRTG Hosted Monitor.

SMTP Relay Port

This setting is only visible if you select Use SMTP relay server (recommended in LANs/NATs) or Use two SMTP relay servers (primary and fallback server) above. Enter the port for the connection to the SMTP server. The default port is 25.

i_podThis option is not available in PRTG Hosted Monitor.

SMTP Relay Authentication

This setting is only visible if you select Use SMTP relay server (recommended in LANs/NATs) or Use two SMTP relay servers (primary and fallback server) above. Select the kind of authentication that the SMTP server requires:

  • Use no authentication: Use SMTP without authentication.
  • Use standard SMTP authentication: Use standard authentication.
  • Use SASL authentication: Use secure authentication via Simple Authentication and Security Layer (SASL).

i_podThis option is not available in PRTG Hosted Monitor.

SMTP Relay User Name

This setting is only visible if you select Use standard SMTP authentication or Use SASL authentication above. Enter a valid user name.

i_podThis option is not available in PRTG Hosted Monitor.

SMTP Relay Password

This setting is only visible if you select Use standard SMTP authentication or Use SASL authentication above. Enter a valid password.

i_podThis option is not available in PRTG Hosted Monitor.

Connection Security

This setting is only visible if you select Use SMTP relay server (recommended in LANs/NATs) or Use two SMTP relay servers (primary and fallback server) above. Define the connection security for SMTP connections:

  • Use SSL/TLS if the server supports it: Use a Secure Sockets Layer (SSL)/Transport Layer Security (TLS) secured connection.
  • Do not use connection security: Use an unsecure connection with plain text transfer.

i_podThis option is not available in PRTG Hosted Monitor.

SSL/TLS Method

This setting is only visible if you select Use one SMTP relay server (recommended in LANs/NATs) and Use SSL/TLS if the server supports it above. Select the SSL or TLS version that the SMTP server supports. Choose from:

  • SSLv2 or SSLv3 (default)
  • SSLv3
  • TLS 1.0
  • TLS 1.1
  • TLS 1.2

i_round_blueThis is only relevant for secure connections. If you do not get a connection, try a different setting.

i_podThis option is not available in PRTG Hosted Monitor.

SMTP Relay Server (Fallback)

This setting is only visible if you select Use two SMTP relay servers (primary and fallback server) above. Enter the IP address or DNS name of the fallback SMTP relay server.

i_podThis option is not available in PRTG Hosted Monitor.

SMTP Relay Port (Fallback)

This setting is only visible if you select Use two SMTP relay servers (primary and fallback server) above. Enter the port for the connection to the fallback SMTP server. The default port is 25.

i_podThis option is not available in PRTG Hosted Monitor.

SMTP Relay Authentication (Fallback)

This setting is only visible if you select Use two SMTP relay servers (primary and fallback server) above. Select the kind of authentication that the fallback SMTP server requires:

  • Use no authentication: Use SMTP without authentication.
  • Use standard SMTP authentication: Use standard authentication.
  • Use SASL authentication: Use secure authentication via Simple Authentication and Security Layer (SASL).

i_podThis option is not available in PRTG Hosted Monitor.

SMTP Relay User Name (Fallback)

This setting is only visible if you select Use two SMTP relay servers (primary and fallback server) and Use standard SMTP authentication or Use SASL authentication above. Enter a valid user name.

i_podThis option is not available in PRTG Hosted Monitor.

SMTP Relay Password (Fallback)

This setting is only visible if you select Use two SMTP relay servers (primary and fallback server) and Use standard SMTP authentication or Use SASL authentication above. Enter a valid password.

i_podThis option is not available in PRTG Hosted Monitor.

Connection Security (Fallback)

This setting is only visible if you select Use two SMTP relay servers (primary and fallback server) above. Define the connection security for SMTP connections:

  • Use SSL/TLS if the server supports it: Use a Secure Sockets Layer (SSL)/Transport Layer Security (TLS) secured connection.
  • Do not use connection security: Use an unsecure connection with plain text transfer.

i_podThis option is not available in PRTG Hosted Monitor.

SSL/TLS Method (Fallback)

This setting is only visible if you select Use two SMTP relay servers (primary and fallback server) and Use SSL/TLS if the server supports it above. Select the SSL or TLS version that the SMTP server supports. Choose from:

  • SSLv2 or SSLv3 (default)
  • SSLv3
  • TLS 1.0
  • TLS 1.1
  • TLS 1.2

i_round_blueThis is only relevant for secure connections. If you do not get a connection, try a different setting.

i_podThis option is not available in PRTG Hosted Monitor.

Test SMTP Settings

Click Test SMTP Settings to test your SMTP notification delivery configuration.

  • Email Address: Enter an email address to send the test email notification to.
  • Subject: Enter a subject for the test email notification.

SMS Delivery

i_round_blueAlthough PRTG has built-in support for the application programming interface (API) of some SMS providers, we cannot officially provide support for them. If you have technical questions about SMS delivery beyond PRTG, contact your SMS provider directly.

i_round_blueInstead of using a preconfigured provider, you can use a custom URL that enables you to use extended parameters. This is also an alternative to using providers for which we offer preconfigured options.

i_round_blueYou need an internet connection to send text messages via the HTTP API.

i_square_cyanFor information about sending SMS via separate hardware using third-party software, see the Knowledge Base: How can I send SMS text message notifications via a modem or a mobile phone with PRTG?.

SMS Delivery

SMS Delivery

Setting

Description

Configuration Mode

Define a mode for the SMS delivery configuration:

  • Disable SMS delivery: Do not use SMS delivery.
  • Select an SMS provider from a list of providers: Select a provider from a list below.
  • Enter a custom URL for a provider not listed: Use a different provider and manually enter the custom URL below.

Service Provider

This setting is only visible if you select Select an SMS provider from a list of providers above. Select a service provider from the list. Choose between:

  • BulkSMS All regions (except South Africa): Enter a User Name and Password below.
    • URL: https://www.bulksms.co.uk:443/eapi/submission/send_sms/2/2.0
  • Port: 443
  • BulkSMS South Africa: Enter a User Name and Password below.
    • URL: https://bulksms.2way.co.za:443/eapi/submission/send_sms/2/2.0
    • Port: 443
  • Agile Telecom: Enter a User Name and Password below.
    • URL: http://agiletelecom.com/smshurricane3.0.asp
    • Port: 80
  • Esendex: Enter a User Name, Password, and Account below.
    • URL: https://www.esendex.com/secure/messenger/formpost/SendSMS.aspx
    • Port: 443

i_round_blueSome providers might require a port configuration in your firewall. Use the respective port from the list above.

User Name

This setting is only visible if you select Select an SMS provider from a list of providers above. Enter a user name for the service provider account.

Password

This setting is only visible if you select Select an SMS provider from a list of providers above. Enter a password for the service provider account.

Account

This setting is only visible if you select Select an SMS provider from a list of providers and Esendex above. Enter the account number or the API ID to connect your account if your provider asks you to register. Enter a string or leave the field empty.

Custom URL

This setting is only visible if you select Enter a custom URL for a provider not listed above. From the documentation of your SMS provider, enter the service URL that it uses to send SMS messages.

Use the following placeholders for the recipient phone number and the text message:

  • %SMSNUMBER
  • %SMSTEXT

i_round_blueUse the GET method to request the custom URL. POST requests are not supported.

HTTP Authentication

This setting is only visible if you select Enter a custom URL for a provider not listed above. Select if PRTG uses HTTP basic authentication when it calls the custom URL of the SMS provider:

  • Do not use HTTP basic authentication (default)
  • Use HTTP basic authentication

i_round_blueHTTP basic authentication is necessary if the custom URL looks like this https://[username]:[password]@my.custom.sms.provider/.

Custom SNI

This setting is only visible if you select Enter a custom URL for a provider not listed above.

Define if PRTG sends the Server Name Identification (SNI) extension to the Transport Layer Security (TLS) protocol along with the HTTP request:

  • Do not send SNI (default): PRTG does not send the SNI when it executes the HTTP action.
  • Send SNI: PRTG sends the SNI when it calls the target URL. Specify the SNI below.

Encoding for SMS

This setting is only visible if you select Enter a custom URL for a provider not listed above. Define the encoding of the URL string that PRTG sends to the SMS provider:

  • ANSI local system code page (default)
  • UTF-8
  • UTF-16

Virtual Host (SNI)

Enter the SNI name that the endpoint configuration requires. Usually, this is the fully qualified domain name (FQDN) of the virtual host.

Maximum Length of Text

Some SMS providers do not allow SMS messages that exceed a certain amount of characters. PRTG restricts the number of characters according to the length specified in this field. A value of 0 means that PRTG sends the entire SMS.

Test SMS Settings

Click Test SMS Settings to test your SMS notification delivery configuration.

  • Number: Enter a phone number to send the test SMS notification to.
  • Message: Enter a message for the test SMS notification.

i_round_blueThe notification methods Send SMS/Pager Message and Execute HTTP Action use the central proxy settings of the PRTG core server. For details, see section Core & Probes (section Proxy Configuration).

i_round_redSave your settings. If you change tabs or use the main menu without saving, all changes to the settings are lost.

More

i_square_blueKNOWLEDGE BASE

What security features does PRTG include?

How can I send SMS text message notifications via a modem or a mobile phone with PRTG?

Which URLs does PRTG use for its preconfigured SMS providers?

Why do I get a connection timeout message when sending SMS via bulksms?

How can PRTG send instant messages to Jabber, ICQ, MSN, Yahoo, etc., using external software?

Can Gmail / Google Apps / G-Suite be used for SMTP relay?

How can I enable notification delivery logging?

Can I use Microsoft Office 365 as SMTP relay server for PRTG email delivery?

 

i_square_bluePAESSLER WEBSITE

FAQ – PRTG Hosted Monitor

You can find custom notification scripts in the PRTG Sensor Hub

Setup

Others

There are some settings that you must make in the PRTG Administration Tool. For more details, see the sections: