Alerting rules can use the Mustache template syntax ({{variable name}}) to pass values when the actions run.

Common variablesedit

The available variables differ by rule type, however there are some common variables:

Some cases exist where the variable values will be "escaped" when used in a context where escaping is needed. For example:

Mustache also supports "triple braces" of the form {{{variable name}}}, which indicates no escaping should be done at all. Use this form with caution, since it could end up rendering the variable content such that the resulting parameter is invalid or formatted incorrectly.

Generaledit

All rule types pass the following variables:

Action frequency: Summary of alertsedit

If the rule’s action frequency is a summary of alerts, it passes the following variables:

Action frequency: For each alertedit

If the rule’s action frequency is not a summary of alerts, it passes the following variables:

Contextedit

If the rule’s action frequency is not a summary of alerts, the rule defines additional variables as properties of the variable context. For example, if a rule type defines a variable value, it can be used in an action parameter as {{context.value}}.

For diagnostic or exploratory purposes, action variables whose values are objects, such as context, can be referenced directly as variables. The resulting value will be a JSON representation of the object. For example, if an action parameter includes {{context}}, it will expand to the JSON representation of all the variables and values provided by the rule type. To see all alert-specific variables, use {{.}}.

For situations where your rule response returns arrays of data, you can loop through the context:

{{#context}}{{.}}{{/context}}

For example, looping through search result hits:

triggering data was:
{{#context.hits}} - {{_source.message}}
{{/context.hits}}

Enhancing Mustache variablesedit

You can enhance the values contained in Mustache variables when the Mustache template is rendered by rendering objects as JSON or by using Mustache lambdas.

Rendering objects as JSONedit

Some connectors (such as the Webhook connector) expect JSON values to be passed as parameters when the connector is invoked. The following capabilities are available:

Using Mustache lambdasedit

Mustache lambdas provide additional rendering capabilities for Mustache templates. A Mustache lambda is formatted like a Mustache section. For example:

{{#EvalMath}} round(context.value, 1) {{/EvalMath}}

In that example, the lambda EvalMath is passed the text round(context.value, 1) and renders a rounded value of the context.value variable. This pattern is used by all the provided Mustache lambdas described in the subsequent sections.

EvalMathedit

The EvalMath lambda will evaluate the text passed to it as TinyMath functions.

For example, when the Mustache variable context.value is 3.1234, the following template will render as 3.1:

{{#EvalMath}} round(context.value, 1) {{/EvalMath}}

This lambda can access Mustache variables without having to wrap them in {{}}. However, if the value is in a string form (for example, an Elasticsearch numeric field whose source was indexed as a string), or could be escaped, escaping the value with triple quotes should allow this to work. For example, if the Mustache variable context.value is "3.1234", the following template will render as 3.1:

{{#EvalMath}} round( {{{context.value}}} , 1) {{/EvalMath}}

ParseHjsonedit

The ParseHjson lambda provides ease-of-use capabilities when constructing JSON objects. Hjson is a syntax extension to JSON. It has the following features:

To use it, surround your Hjson content with {{#ParseHjson}}...{{/ParseHjson}}. For example:

{{#ParseHjson}}
{
  # add the rule id and name to the JSON document
  ruleId:   "{{rule.id}}"
  ruleName: "{{rule.name}}"
}
{{/ParseHjson}}

When rendered, this template will generate:

    {
      "ruleId": "<the rule id is here>",
      "ruleName": "<the rule name is here>"
    }

FormatDateedit

The FormatDate lambda provides date formatting capabilities. Dates can be formatted in an arbitrary time zone and with an arbitrary format string.

To use it, surround the date and formatting parameters with {{#FormatDate}}...{{/FormatDate}}.

The format of the text passed to the lambda is: <date>; <time zone>; <date format>, where semicolons (;) separate each parameter. The <date> parameter is required; the <time zone> and <date format> parameters are optional. The default time zone is "UTC" and the default date format is "YYYY-MM-DD hh:mma". For example, the following templates all render the same value:

    {{#FormatDate}} {{{timestamp}}} {{/FormatDate}}
    {{#FormatDate}} {{{timestamp}}} ; UTC {{/FormatDate}}
    {{#FormatDate}} {{{timestamp}}} ; UTC; YYYY-MM-DD hh:mma {{/FormatDate}}
    {{#FormatDate}} {{{timestamp}}} ; ; YYYY-MM-DD hh:mma {{/FormatDate}}

The <time zone> parameter must be a valid time zone identifier as listed in TZ database time zone names, such as "America/New_York".

The <date format> parameter must be a valid date format string as described in the Moment format() documentation. For example, the date format "YYYY-MM-DD hh:mma" will render in the following format: "2023-04-24 11:21pm".

The date value itself should usually be referenced with triple braces since some characters in date strings may contain values that are escaped, which would prevent them from being parsed as dates.

Mustache examplesedit

This example demonstrates a Mustache template for an email action sent from an Elasticsearch query rule. The template references the following Mustache variables:

For example, if you have data like this available as Mustache variables:

{
  "date": "2023-04-27T22:40:34.153Z",
  "context": {
    "title": "rule 'esq' matched query for group host-2",
    "conditions": "Number of matching documents for group \"host-2\" is less than 1000",
    "link": "https://example.com/this-will-link-to-Discover",
    "hits": [
      {
        "_source": {
          "event": {
            "provider": "alerting",
            "action": "active-instance",
            "duration": "96023000000"
          }
        }
      },
      {
        "_source": {
          "@timestamp": "2023-04-27T22:40:22.251Z",
          "event": {
            "provider": "alerting",
            "action": "execute-action"
          }
        }
      }
    ]
  }
}

You can create the following Mustache template in the email action for your rule:

# {{context.title}} 

{{#FormatDate}} {{{date}}} ; America/New_York {{/FormatDate}} 

{{context.conditions}}

**documents** _[view in Discover]({{{context.link}}})_ 

| provider | action | duration | 
| -------- | ------ | -------- |
{{#context.hits}}{{#_source.event}}| {{provider}} | {{action}} | {{#duration}}{{#EvalMath}} round( {{{duration}}} / 1000 / 1000 / 1000 ) {{/EvalMath}} sec{{/duration}} {{^duration}}-n/a-{{/duration}} |{{/_source.event}}
{{/context.hits}}

When rendered into Markdown and then HTML and viewed in an email client, it looks like this: