Date: Fri, 29 Mar 2024 05:54:56 +0000 (UTC) Message-ID: <1125277458.5615.1711691696752@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5614_598075302.1711691696742" ------=_Part_5614_598075302.1711691696742 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Contents
up.time's standard alert format should be well suited for most alerting = needs. However, you can modify the alert content by adding or removing vari= ables from one of the three custom alert templates. For more information on= the variables, see Alert Profile and Action Profile Variables and&nb= sp;Custom Alert Format Va= riables
There are three custom alert formats:
Small Template Contains the date and time of the alert, as well as t= he names and status of the service and host for which the alert was generat= ed. This corresponds to the template used for pager alerts, as shown below:=
$SERVIC= ESTATE$ Alert $DATETIME$ Type: $TYPE$ Service: $SERVICENAME$ ($SERVICESTATE$) Host: $HOSTNAME$ ($HOSTSTATE$)
Medium Template
Contains the information in the small template= , as well as an expanded subject line, the type of notification, and output= from the Service Monitor. This corresponds to the template used for email = alerts, as shown below:
up.time= Alert - $SERVICENAME$ -> $SERVICESTATE$ Notification type: $TYPE$ $DATETIME$ Host: $HOSTNAME$ ($HOSTSTATE$) Service:$SERVICENAME$ Service State: $SERVICESTATE$ Output: $OUTPUT$
Long Template
Contains the information in the medium template,= as well as the status of the host, as shown below:
up.time= Alert - $DATETIME$ - $SERVICENAME$ -> $SERVICESTATE$ Date: $DATE$ Time: $TIME$ Date & Time: $DATETIME$ Hostname: $HOSTNAME$ Host State: $HOSTSTATE$ Service: $SERVICENAME$ Service State: $SERVICESTATE$ Notification Type: $TYPE$ Output: $OUTPUT$
To define a custom alert format: