<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Notification Delivery
In the Notification Delivery settings, 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.
If you use PRTG on premises and open the system administration page from a different administration page, PRTG asks you to enter your credentials again for security reasons if 15 minutes (900 seconds) have passed since your last credential-based login. A dialog box appears. Enter your Login Name and Password for PRTG in the corresponding fields and confirm to continue.
Note
You have to take the following four steps to set up and use notifications:
- Check and set up the Notification Delivery settings if you use PRTG on premises. These settings define how PRTG sends messages.
- Check and set up Notification Contacts for the user accounts. These contacts define the recipients to which PRTG sends notifications.
- Check and set up several Notification Templates. These templates define the notification methods and their content.
You can also check or edit notification templates via the Notification Triggers tab. For more information, see section Notification Triggers Settings.
- Check and set up Notification Triggers Settings for objects. These triggers define when PRTG sends notifications.
Usually, 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 (because of an email server outage or for other reasons), 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.
See sections Notifications Based on Sensor Limits Step by Step and Notifications Based on Libraries Step by Step for step-by-step guides that describe potential notification setups.
Custom notification scripts are also available in the PRTG Sensor Hub.
SMTP Delivery
This 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.
|
|
SMTP Delivery Mechanism
|
Define how PRTG sends emails using the Simple Mail Transfer Protocol (SMTP):
- Direct delivery using built-in email relay server (default): Use the SMTP relay server built into PRTG. 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 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 primary and one as fallback server. Enter data below.
If you monitor the IT infrastructure in your network address translation (NAT) or LAN, using your own LAN-based relay server ensures faster delivery of notification emails.
This 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
|
Enter an email address to use as sender of all emails. This setting is global and applies to all email notifications by default. You can override the sender email in the settings of individual notifications.
|
Sender Name
|
Enter a name to use as sender of all emails. This setting is global and applies to all email notifications by default. You can override the sender name in the settings of individual notifications.
If 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 the HELO Ident for SMTP. This must be a unique name, preferably the Domain Name System (DNS) name of the PRTG core server system. See SMTP RFC 2821: The sender-SMTP must ensure that the domain parameter in a HELO command is a valid principal host domain name for the client host.
This option is not available in PRTG Hosted Monitor.
|
SMTP Relay Server
|
This setting is only visible if you select SMTP relay server above. Enter the IP address or DNS name of the SMTP relay server.
This option is not available in PRTG Hosted Monitor.
|
SMTP Relay SMTP Port
|
This setting is only visible if you select SMTP relay server above. Enter the port number that the SMTP relay server runs on. The standard port is 25.
This option is not available in PRTG Hosted Monitor.
|
SMTP Relay Authentication
|
This setting is only visible if you select SMTP relay server above. Select the kind of authentication required for the SMTP server:
- No authentication is required: Use SMTP without authentication.
- Use standard SMTP authentication: Use standard authentication.
- SASL authentication is required: Use secure authentication via Simple Authentication and Security Layer (SASL).
This option is not available in PRTG Hosted Monitor.
|
SMTP Relay User Name
|
This setting is only visible if you select Use standard SMTP authentication above. Enter a valid user name.
This option is not available in PRTG Hosted Monitor.
|
SMTP Relay Password
|
This setting is only visible if you select Use standard SMTP authentication above. Enter a valid password.
This option is not available in PRTG Hosted Monitor.
|
Connection Security
|
This setting is only visible if you select SMTP relay server above. Define the connection security for SMTP connections:
- Use SSL/TLS if supported (default): 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.
This option is not available in PRTG Hosted Monitor.
|
SSL/TLS Method
|
This setting is only visible if you select SMTP relay server and connection security above. It is only relevant for secure connections. Select the SSL or TLS version that your SMTP device supports. We recommend that you use this option. If you do not get a connection, try with a different setting. Choose from:
- SSLv2 or SSLv3 (default)
- SSLv3
- TLS 1.0
- TLS 1.1
- TLS 1.2
This option is not available in PRTG Hosted Monitor.
|
SMTP Relay Server (Fallback)
|
These fields are only visible if you select the option for two SMTP relay servers above. See also the settings that you made for your primary SMTP relay server.
This option is not available in PRTG Hosted Monitor.
|
SMTP Relay SMTP Port (Fallback)
|
SMTP Relay Authentication (Fallback)
|
Connection Security (Fallback)
|
SSL/TLS Method (Fallback)
|
SMTP Relay User Name (Fallback)
|
SSL Method (Fallback)
|
SMTP Relay User Name (Fallback)
|
SMTP Relay Password (Fallback)
|
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.
This option is not available in PRTG Hosted Monitor.
|
SMS Delivery
Although PRTG has built-in support for the application programming interface (API) of some SMS providers, we cannot officially provide support regarding these SMS service providers. If you have technical questions about SMS delivery beyond PRTG, contact your SMS provider directly.
Instead of using a preconfigured provider, you can always use a custom URL that enables you to use extended parameters (this is also an alternative when using providers for which we offer preconfigured options).
You need an internet connection to send text messages via the HTTP API.
For 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?
|
|
Configuration Mode
|
Define how you want to select an SMS provider:
- 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 enter the service URL manually 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)
- URL: https://www.bulksms.co.uk:443/eapi/submission/send_sms/2/2.0
- Port: 443
- URL: https://bulksms.2way.co.za:443/eapi/submission/send_sms/2/2.0
- Port: 443
- URL: http://agiletelecom.com/smshurricane3.0.asp
- Port: 80
- URL: https://www.esendex.com/secure/messenger/formpost/SendSMS.aspx
- Port: 443
Some providers might require a port configuration in your firewall. Use the respective port from the list above.
|
User
|
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.
|
API ID / Account
|
This setting is only visible if you select Select an SMS provider from a list of providers above. Some providers need an additional API ID or account information. If provided, enter it here. 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 is used to send SMS messages.
Use the following placeholders for the recipient phone number and the text message:
Use 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 your SMS provider:
- Do not use HTTP basic authentication (default)
- Use HTTP basic authentication
HTTP basic authentication is necessary if the custom URL reads like 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.
Select 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 executing the HTTP action.
- Send SNI: PRTG sends the SNI when calling the target URL. Specify the SNI below.
|
Virtual Host (SNI)
|
This setting is only visible if you enable Send SNI above. Enter the SNI name that your endpoint configuration requires. Usually, this is the fully qualified domain name (FQDN) of the virtual host.
|
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 your provider:
- ANSI local system code page (default)
- UTF-8
- UTF-16
|
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 the SMS is sent at its full length.
|
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.
|
The notification methods Send SMS/Pager Message and Execute HTTP Action use the central proxy settings defined for your PRTG core server. For details, see section Core & Probes (section Proxy Configuration).
Save your settings. If you change tabs or use the main menu without saving, all changes to the settings are lost.
More
KNOWLEDGE 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?
PAESSLER 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: