PRTG Manual: Placeholders for Notifications
Here you can find a list of all placeholders for notifications. You can use placeholders in different settings fields of a notification when editing notification templates.
In this section:
Notification |
Settings field |
|---|---|
Send Email |
|
Add Entry to Event Log |
Message |
Send SMS/Pager Message |
Message |
Execute HTTP Action |
Payload if you select the options POST, PUT, or PATCH |
Execute Program |
Parameters |
Send Syslog Message |
Message |
Send SNMP Trap |
Message |
Send Amazon Simple Notification Service Message |
Message |
Assign Ticket |
|
Send Push Notification |
Message |
Send Microsoft Teams Message |
|
Send Slack Message |
|
Send MQTT Publish Notification |
Message |
Placeholders are not case-sensitive.
Depending on where you use a placeholder in a notification, PRTG might resolve the placeholder differently. A resolved placeholder in the body of a notification, for example, can contain more information compared to when PRTG resolves the same placeholder in the subject of a notification. The reason for this is to save space in the subject line.
Placeholders in Summarized Notifications
Placeholders in summarized notifications have limited functionality:
- PRTG does not resolve placeholders in the subject field of summarized notifications if more than one trigger was evoked during the summarized time span. An exception are the placeholders %sitename and %summarycount. These are always resolved in summarized notifications.
- If only one event is triggered during the time span you defined, PRTG does not send a summarized notification, it only sends a common notification. A summarized notification requires at least two triggered events.
Placeholder |
Resolved Content |
Synonym |
Comment |
|---|---|---|---|
%colorofstate |
Color of the current object status (hex code) |
|
Might not work in older versions. |
%company |
Copyright string of Paessler GmbH |
|
|
%comments |
Comments entered for the sensor |
%commentssensor |
As of PRTG 15.4.21, resolved placeholders contain the heading Sensor Comments. |
%commentssensor |
Comments entered for the sensor |
%comments |
As of PRTG 15.4.21, resolved placeholders contain the heading Sensor Comments. |
%commentsdevice |
Comments entered for the parent device |
|
As of PRTG 15.4.21, resolved placeholders contain the heading Device Comments. |
%commentsgroup |
Comments entered for the parent group |
|
As of PRTG 15.4.21, resolved placeholders contain the heading Group Comments. |
%commentsprobe |
Comments entered for the parent probe |
|
Available as of PRTG 12.4. As of PRTG 15.4.21, resolved placeholders contain the heading Probe Comments. |
%coverage |
Covered time span |
|
Might not work in older versions. |
%cumsince |
Since when data has been accumulated |
|
|
%date |
An event's date in the time zone of the PRTG core server system |
|
|
%datetime |
An event's date and time in the time zone of the PRTG core server system |
|
|
%device |
Name of the device in which the event was triggered |
%server |
|
%deviceid |
ID number of the device in which the event was triggered |
|
|
%down |
Time the item was down |
|
|
%downtime |
Accumulated downtime |
|
|
%elapsed_lastcheck |
Elapsed time since the sensor's last scan |
|
Available as of PRTG 20.1.57. |
%elapsed_lastdown |
Elapsed time since the sensor last showed a Down status |
|
Available as of PRTG 20.1.57. |
%elapsed_lastup |
Elapsed time since the sensor last showed an Up status |
|
Available as of PRTG 20.1.57. |
%group |
Group in which the event was triggered |
|
|
%groupid |
ID number of the group in which the event was triggered |
|
|
%history |
History of sensor events |
|
|
%home |
URL of the PRTG web server |
|
|
%host |
IP or DNS name of the device that triggered the event |
|
As of PRTG 13.x.7, the placeholder can be used as Agent IP in SNMP trap notifications sent by PRTG. |
%iconofstate |
File name including the extension of the icon for the current object status |
|
Might not work in older versions. |
%lastcheck |
Point in time of the sensor's last scan including time stamp |
|
|
%lastdown |
Point in time when the sensor last showed a Down status, including the time stamp |
|
|
%lastmessage |
Message that the sensor sent the last time |
%message |
|
%laststatus |
Current sensor status |
|
Available as of PRTG 20.1.57. |
%lastup |
Point in time when the sensor last showed an Up status, including the time stamp |
|
|
%lastvalue |
Value that the sensor sent the last time |
|
|
%linkprobe |
URL of the probe that triggered the event |
|
Might not work in older versions. |
%linkgroup |
URL of the group that triggered the event |
|
Might not work in older versions. |
%linkdevice |
URL of the device that triggered the event |
|
Might not work in older versions. |
%linksensor |
URL of the sensor that triggered the event |
|
Might not work in older versions. |
%location |
Location of the device or server for which the event was triggered |
|
|
%message |
Message that the sensor sent the last time |
%lastmessage |
|
%name |
Name of the sensor that triggered the event, including the sensor type |
%sensor |
|
%nodename |
Name of the node if PRTG runs in a cluster |
|
Might not work in older versions. |
%objecttags |
All tags of a sensor |
|
Available as of PRTG 20.1.56. |
%parenttags |
All tags of a sensor's parent objects |
|
Available as of PRTG 20.1.56. |
%prio |
A sensor's priority setting |
%priority |
|
%priority |
A sensor's priority setting |
%prio |
|
%probe |
Probe under which the event was triggered |
|
|
%probeid |
ID number of the probe under which the event was triggered |
|
|
%programname |
Official name of PRTG |
|
|
%programversion |
Program version of PRTG |
|
|
%sensor |
Name of the sensor that triggered the event, including the sensor type |
%name |
|
%sensorid |
ID number of the sensor that triggered the event |
|
|
%server |
Name of the device under which the event was triggered |
%device |
|
%serviceurl |
Service URL configured for the device under which the event was triggered |
|
Available as of PRTG 9.1. |
%settings |
Miscellaneous sensor settings, such as the user name for Windows, HTTP, POP3 credentials, and so on |
|
|
%shortname |
Name of the sensor that triggered the event |
|
|
%since |
Point in time since the current object status has been active |
%statesince |
|
%sitename |
Name of the PRTG web server |
|
|
%statesince |
Point in time since the current object status has been active |
%since |
|
%status |
Old sensor status and current sensor status |
|
|
%summarycount |
Number of events triggered during the defined time span |
|
|
%syslogerrors |
Max. last 20 syslog entries before the notification trigger |
|
Available as of PRTG 14.x.10.
|
%syslogmessages |
Max. last 20 syslog entries before the notification trigger |
|
Available as of PRTG 14.x.10.
|
%syslogwarnings |
Max. last 20 syslog entries before the notification trigger |
|
Available as of PRTG 14.x.10.
|
%systemdatetime |
Date and time when the notification was sent in the time zone of the PRTG core server system |
|
|
%tags |
All tags of a sensor and its parent objects |
|
Available as of PRTG 20.1.56. |
%time |
An event's time in the time zone of the PRTG core server system |
|
|
%timezone |
Time zone name of the PRTG core server system |
|
|
%toaddress |
Address to which the notification was sent |
|
|
%traperrors |
Max. last 20 SNMP trap entries before the notification trigger |
|
Available as of PRTG 14.x.10.
|
%trapmessages |
Max. last 20 SNMP trap entries before the notification trigger |
|
Available as of PRTG 14.x.10.
|
%trapwarnings |
Max. last 20 SNMP trap entries before the notification trigger |
|
Available as of PRTG 14.x.10.
|
%uptime |
Accumulated uptime |
|
|
As of PRTG 15.4.21, PRTG uses default content in HTML email notifications. You can still change the content of emails in plain text in the Send Email notification settings and also use placeholders there.
As of PRTG 16.x.24, the placeholder %state has been deprecated. You can use the placeholder %status with the same functionality instead.
For a list of placeholders that are available for EXE/Script and other custom sensors, as well as for command-line parameters, see section Custom Sensors.
