Alerting system variables

We’re changing our user interface. Some info may not yet be up to date. Please check From classic to new UI.

This article contains an overview of all available System variables, which can be used to populate the outgoing alert message with relevant information about things like the monitor that caused it, what error occurred, or the alert itself. For more information on how to make use of these system variables, please read our article on building the right message content.

In short, to use the variables listed here, they will have to be included in the message content wrapped in double curly brackets. As an example: {{@alert.alertGuid}}.

VariableDescriptionExample value
@alert.alertGuidUnique id of this alertcbfc7769-edb2-46a7-89d0-1e1b1fb0815b
@alert.typeThe type of this alert message:
  • Alert: a new error was detected.
  • Ok: the original error has been resolved.
  • Reminder: the original error is still ongoing.
Alert | Ok | Reminder
@alert.timestampUtcThe date and time of the alert, expressed in UTC time, and formatted as ISO 86012018-11-08T16:26:58
@alert.timestampThe same date and time as @alert.timestampUtc, but in the timezone of your account. Also formatted as ISO 86012018-11-08T10:26:58
@alert.firstErrorUtcThe date and time of the original error that triggered this alert, expressed in UTC time, and formatted as ISO 86012018-11-08T16:21:58
@alert.firstErrorThe same date and time as @alert.firstErrorUtc, but in the timezone of your account. Also formatted as ISO 86012018-11-08T10:21:58
@alert.responseBodyContains the response body received when it's available. Note that the response body may contain characters that need to be encoded, e.g. using @JsonEncode or @XmlEncode. The response body will be truncated when it's larger than 1 MB.{"Status": "error"}
@alert.timestampUtcFormattedThe date and time of the alert, expressed in UTC time, and formatted in the culture of your account8/28/2020 10:23 PM
@alert.timestampFormattedThe same date and time as @alert.timestampUtc, but in the timezone and culture of your account8/28/2020 12:23 PM
@alert.firstErrorUtcFormattedThe date and time of the original error that triggered this alert, expressed in UTC time, and formatted in the culture of your account8/28/2020 10:23 PM
@alert.firstErrorFormattedThe same date and time as @alert.firstErrorUtc, but in the timezone and culture of your account8/28/2020 12:23 PM
@alert.errorTypeId

The error type id of the error that triggered this alert, see Error types for a list of error types

5407
@alert.descriptionText description of the error that triggered this alertDNS expected result not found
@alert.firstErrorCheckUrlThe URL of a deep link that takes you to the details of the error that triggered this alerthttps://app.uptrends.com/Report/ProbeLog/Check/30833627687
@alert.firstErrorCheckIdThe Id of the error that triggered this alert30833627687
@alert.serverIpv4The IPv4 address of the server on which the check was performed178.217.84.4
@alert.serverIpv6The IPv6 address of the server on which the check was performed2a02:2658:103e:4:461:81bb:adbe:82a5
@alert.resolvedIpAddressThe ip address that was used to perform the check. Can be either a ipv4 or a ipv6 address178.217.84.4 OR 2a02:2658:103e:4:461:81bb:adbe:82a5
@alert.firstErrorDescriptionThe error description of the first monitor check that received the errorDNS expected result not found
@alertDefinition.guidThe unique id of the alert definition that was used to generate this alert2C97E464-6112-435B-8C8D-6DEF1E18273A
@alertDefinition.nameThe name of the alert definition that was used to generate this alertDefault Alert
@escalationLevel.idThe id of the escalation level that was used to generate this alert1
@escalationLevel.messageThe custom message that was specified in the escalation levelPlease use checklist THX-1138 to investigate this issue.
@incident.keyUnique id of the incident this alert belongs to. An error alert and an Ok alert share the same incident keyba8ffcb7-5de0-489e-b649-f00f0b447e80-0-30099055746
@monitor.monitorGuidThe unique id of the monitor in your account that triggered this alert849b2046-213d-43ad-9efc-5af1faaeb222
@monitor.nameThe name of the monitor in your account that triggered this alertGalacticResorts.com - DNS
@monitor.notesAny custom notes that were filled in the monitor settingsPlease check Amazon Route53 DNS entries
@monitor.typeContains the type of the monitorTransaction
@monitor.urlThe URL or network address this monitor is checkinghttps://galacticresorts.com
@monitor.dashboardUrlThe URL of a deep link that takes you to the dashboard for this monitorhttps://app.uptrends.com/Probe/Dashboard?probeGuids=fe1ad4a2-57c1-49db-af16-ff3a6beaa8d4
@monitor.editUrlThe URL of a deep link that takes you to the settings for this monitorhttps://app.uptrends.com/Report/Probe?probeGuid=fe1ad4a2-57c1-49db-af16-ff3a6beaa8d4
@account.accountIdYour Uptrends account id299840
By using the Uptrends website, you consent to the use of cookies in accordance with our Cookie Policy.