Related Documentation | \nVersion of up.time \naffected | \nAffected Platforms | \n
\n | \n4.4 or later | \nAll | \n
When up.time sends an alert, it uses a specific template for the subject line and body of the alert. While this standard 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.
\n \nThe variables are the building blocks of a custom alert format and can be added or removed to suit your needs. The table below explains the variables used in a custom alert format.
\n \nVariable | \n\tDefinition | \n
$DISPLAYNAME$ | \n\tThe name of the entity as it appears in the up.time Web interface.
\n\t A system 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. \n\t |
\n
$DATETIME$ | \n\tThe date and time at which the alert was generated. This appears in the subject line of the message. | \n
$SERVICENAME$ | \n\tThe name of the service, along with the name of the host for which the alert has been generated. This appears in the subject line of the message. | \n
$SERVICESTATE$ | \n\tOne of the following: \n
This appears in the subject line of the message. |
\n
$DATE$ | \n\tThe date on which the alert was generated. | \n
$TIME$ | \n\tThe time at which the alert was generated. | \n
$HOSTNAME$ | \n\tThe name of the host for which this alert was generated. | \n
$HOSTSTATE$ | \n\tOne of the following: \n
|
\n
$TYPE$ | \n\tThe type of notification:
\n
|
\n
$OUTPUT$ | \n\tThe output of the monitor that generated the alert. | \n