How do I add custom template variables to my monitor message?

For multi-alert monitors, you can add template variables to include information in your alert message that's specific to the tag scope that triggered the alert. This is dependent on the tags you use in the "trigger a separate alert for each" field in Section 1 of your monitor.

For example, if you trigger by each "host" tag, then a number of template variables related to "host" will be available to you in your Section 3, "Say what's happening", such as {{}}, {{host.ip}}, etc. Using those variables, when the alert is triggered, you can be told the name and IP of the specific host that breached the monitor threshold.

But this also works for custom tags as well. If you've added a custom tag that follows the "key:value" syntax, then you can group data by those tag keys. This means you'll be able to apply the tag's "key" to the list of tags that a multi alert will have a separate trigger for. Which in turn means you can use that tag's ".name" variable in your monitor message. (Of course, template variables can get confusing, so take a look at the "use message template variables" button for a list of available variables and a walkthrough of how to use them effectively.)

You can also use these template variables to set conditional contacts and messages within the same monitor.


Here's an example of where a user had a number of hosts tagged by different "creator:" values, e.g, "creator:wes_anderson" and "creator:saint_exupéry". Here, the user was able to set up a multi-alert monitor to trigger a separate alert for each "creator" tag, so they were able to include the {{}} in their monitor message. When this monitor triggers, the recipient of the alert notification will see whether the monitor was triggered by "wes_anderson", "saint_exupéry", or some other "creator" value. 


My tag key has dots in it

A word of warning: the period (".") is a reserved character for monitor template variables syntax. If your tag group's key has a period in it, you will have to hardwire your template variables to include brackets around the full key. For example, if a user were to submit a metric tagged with dot.key.test:five and then set up a multi alert monitor triggered by the dot.ket.test group tag, this user would have to apply the following syntax in order to use the template variable:

This monitor resulted in the following event (tagged by dot.key.test:five):



Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk