Date: Fri, 29 Mar 2024 15:31:56 +0000 (UTC) Message-ID: <1384687541.5815.1711726316848@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5814_664144282.1711726316847" ------=_Part_5814_664144282.1711726316847 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
When Uptime Infrastructure Monitor sends an alert, it uses a spe= cific template for the subject line and body of the alert. While this stand= ard alert format is well suited for most alerting needs, you can modify the= content of the alert by adding or removing variables from one of the three= custom alert templates.
The variables are the building blocks of a custom alert format and can b= e added or removed to suit your needs. The table below explains the variabl= es used in a custom alert format for a more comprehensive guide refer to Alert Prof= ile and Action Profile Variables.
Variable | Definition |
$DISPLAYNAME$ | The name of the entity =
as it appears in the Uptime Infrastructure Monitor Web interface. A syste= m can have a different display name than the hostname. For example, you can= assign the display name Toronto Mail Server to a system with the host name= 10.1.1.6. |
$DATETIME$ | The date and time at wh= ich the alert was generated. This appears in the subject line of the messag= e. |
$SERVICENAME$ | The name of the service= , along with the name of the host for which the alert has been generated. T= his appears in the subject line of the message. |
$SERVICESTATE$ | One of the following:
This appears in the subject line of the message. |
$DATE$ | The date on which the a= lert was generated. |
$TIME$ | The time at which the a= lert was generated. |
$HOSTNAME$ | The name of the host fo= r which this alert was generated. |
$HOSTSTATE$ | One of the following:
|
$TYPE$ | The type of notificatio=
n:=20
|
$OUTPUT$ | The output of the monit= or that generated the alert. |