Notification Templates

When Are Templates Used?

The system uses templates to render Incident when assigning incidents, which may occur in the following scenarios:

Manually create and assign an incident

When an alert event is reported, the system automatically generates an incident and assigns it according to the matched escalation rule

After an incident is created, manually change the assignment (reassign)

System automatically escalates according to escalation rule settings

When reopening a closed incident, reassign according to previous settings

We use Golang template syntax template/html to parse data, enabling you to accomplish any complex rendering requirements.

For documentation, please refer to here, supporting logical conditions, loops, pipelines, and common functions;

We've incorporated the open-source library sprig, which includes hundreds of common functions that you can directly call in templates;

If you wish to introduce more functions, feel free to submit a merge request

How to Configure Notification Templates?

Configure Notification Templates

The system uses the default template when notifying incidents, which cannot be modified. If you need to customize the notification content, you should create a custom template.

Enter the Templates page, click the Create Custom Template button or Copy Default Template, and enter the editing page.

In the editing page, you can edit the content according to the notification channel used, and reference the content in the template can refer to [What Variables Can I Reference?](#What Variables Can I Reference?)

After editing, click the Save button to save the template.

Use Notification Templates

Enter the Channel -> Escalation Rules page, click the Edit button, and enter the editing page.

In the strategy configuration section, you can select the template to use which template for notification, and select the notification template to use.

Other configurations can refer to Escalation Rules Configuration.

After configuration, click the Save button to save the escalation policy.

What Variables Can I Reference?

Variable Reference Examples:

Complete Variable List (Direct Reference):

Field	Type	Required	Description
ID	string	Yes	Incident ID
`Title`	string	Yes	Incident title
`Description`	string	Yes	Incident description, can be empty
DetailUrl	string	Yes	Incident detail page URL
Num	string	Yes	Short incident identifier, for easy visual recognition, may be duplicate
`IncidentSeverity`	string	Yes	Severity level, enum values: Critical, Warning, Info
IncidentStatus	string	Yes	Incident status, enum values: Critical, Warning, Info, Ok
`Progress`	string	Yes	Processing progress, enum values: Triggered, Processing, Closed
`StartTime`	int64	Yes	Trigger time, Unix timestamp in seconds
LastTime	int64	No	Latest event time, latest incorporated event time in associated alerts, Unix timestamp in seconds, default 0
EndTime	int64	No	Recovery time, when all associated alerts recover, the incident will automatically recover and close. Unix timestamp in seconds, default 0
SnoozedBefore	int64	No	Snooze end time, Unix timestamp in seconds, default 0
AckTime	int64	No	First acknowledgment time, Unix timestamp in seconds, default 0
CloseTime	int64	No	Close time, end_time is incident recovery time, close_time is processing progress close time. Incident automatically closes upon recovery, manual closure doesn't affect recovery. Unix timestamp in seconds, default 0
Creator	Person	No	Creator information, not present when automatically generated by system
Closer	Person	No	Closer information, not present when incident recovers automatically
AssignedTo	Assignment	No	Assignment configuration
Responders	[]Responder	No	Responder list, initialized based on assignment configuration, also includes records if non-assigned personnel acknowledge the incident
ChannelID	int64	No	Channel ID, value is 0 when manually creating global incident
ChannelName	string	No	Channel name
GroupMethod	string	No	Grouping method, enum values: n: no grouping, p: rule-based grouping, i: intelligent grouping
`Labels`	map[string]string	No	Label key-value pairs, both Key and Value are strings. No information when manually created, contains first alert's label information when automatically created
AlertCnt	int64	Yes	Number of associated alerts
Alerts	[]Alert	No	Associated alert details, no information when manually created
FireType	string	No	Notification type, enum values: fire: notify, refire: loop notification
IsFlapping	bool	No	Whether in flapping state, i.e., frequent occurrence and recovery, related to convergence configuration
Impact	string	No	Incident impact, filled after incident closure
RootCause	string	No	Root cause, filled after incident closure
Resolution	string	No	Resolution, filled after incident closure

Person (Indirect Reference):

Field	Type	Required	Description
person_id	int64	Yes	Person ID
person_name	string	Yes	Person name
email	string	Yes	Email address

Assignment (Indirect Reference):

Field	Type	Required	Description
PersonIDs	[]string	No	Person ID list, exists only when assigning by person
EscalateRuleID	string	No	Escalation rule ID, exists only when assigning by rule
EscalateRuleName	string	No	Escalation rule name
LayerIdx	string	No	Assignment level, corresponds to escalation rule level index, starts from 0
Type	string	Yes	Assignment type, enum values: assign: assign, reassign: reassign, escalate: escalation assign, reopen: reopen assign

Responder (Indirect Reference):

Field	Type	Required	Description
PersonID	int64	Yes	Person ID
PersonName	string	Yes	Person name
Email	string	Yes	Email address
AssignedAt	int64	Yes	Assignment time, Unix timestamp in seconds, default 0
AcknowledgedAt	int64	No	Acknowledgment time, Unix timestamp in seconds, default 0

Alert (Indirect Reference):

Field	Type	Required	Description
Title	string	Yes	Alert title
Description	string	Yes	Alert description, can be empty
AlertSeverity	string	Yes	Severity level, enum values: Critical, Warning, Info
AlertStatus	string	Yes	Alert status, enum values: Critical, Warning, Info, Ok
Progress	string	Yes	Processing progress, enum values: Triggered, Processing, Closed
StartTime	int64	Yes	Trigger time, Unix timestamp in seconds
EndTime	int64	No	Recovery time, Unix timestamp in seconds, default 0
CloseTime	int64	No	Close time, EndTime is alert recovery time, CloseTime is processing progress close time. Alert automatically closes upon recovery, manual closure doesn't affect alert recovery. Unix timestamp in seconds, default 0
`Labels`	map[string]string	No	Label key-value pairs, both Key and Value are strings

Common Questions

How do I know what label information is available in Labels?

Manually created incidents have no labels

Automatically created incidents have labels, matching the first incorporated alert's labels. Go to the Incidents page, find an incident and view its details to see all label information

Why is the default template used when I configured custom template rendering?

When creating a custom template, the system uses mock data to render the template to check for syntax errors

Mock data has limited coverage and may not match some logic branches in your template during actual operation

If rendering fails, the system will use the default template as a fallback to ensure message delivery

When unsure if a referenced variable exists, it's recommended to use logical conditions to avoid rendering errors, e.g., for the resource label:

Why are characters like ">" escaped in incident titles?

Time variables are timestamps, how do I convert time formats?

How to reference external variables inside a for loop?

How do I extract field values with "." in names, like "obj.instance" in labels?

How do I extract and deduplicate label information from incident-associated alerts?

How do I iterate and print labels?

How do I extract information from JSON fields?

jsonGet function helps extract values from JSON format data using path

Target data for jsonGet function must be valid JSON

Basic usage: {{jsonGet .Labels.xxx "yyy"}}, where xxx must be valid JSON and yyy is a valid extraction path

For JSON path syntax, refer to gjson.dev, where you can input target data and extraction path for real-time preview

10.

如何使用逻辑与、或等条件进行内容显示判断？

# Supported functions
- Use `and` function for logical AND judgment
- Use `or` function for logical OR judgment
- Use `not` function for logical NOT judgment
- Use `eq` function for logical equal judgment
- Use `ne` function for logical not equal judgment
- Use `gt` function for logical greater than judgment
- Use `ge` function for logical greater than or equal judgment
- Use `lt` function for logical less than judgment
- Use `le` function for logical less than or equal judgment

# Example usage
# Use and function for logical AND judgment

{{if and (eq .Labels.resource "cpu") (eq .Labels.metric "cpu_usage")}}
  {{.Labels.resource}} CPU usage exceeds 80%
{{end}}

# Use or function for logical OR judgment
{{if or (eq .Labels.resource "cpu") (eq .Labels.metric "cpu_usage")}}
  {{.Labels.resource}} CPU usage exceeds 80%
{{end}}  

# Use not function for logical NOT judgment
{{if not (eq .Labels.metric "cpu_usage")}}
  {{.Labels.metric}} is not CPU usage
{{end}}

11.

How do I find more functions and their usage examples?

Function list: https://github.com/flashcatcloud/sprig/blob/master/functions.go#L97

Usage examples: Check corresponding _test.go files, e.g., date function test cases at https://github.com/flashcatcloud/sprig/blob/master/date_test.go

Below are specific instructions for each notification channel.

Feishu/Lark App

You need to configure Integration Center-Instant Message-Feishu integration first to send message cards. If custom content is not set, the system default template will be used, rendering all label information:

As shown below:

If you want to display only key label information, you can refer to the code segment below:

We've listed some common labels, you can add or remove as needed

In Feishu app, the system will automatically remove empty rendered lines (due to non-existent labels), so you can configure freely

Dingtalk App

You need to configure Integration Center-Instant Message-Dingtalk integration first to send message cards. If custom content is not set, the system default template will be used, rendering all label information:

As shown below:

If you want to display only key label information, you can refer to the code segment below:

We've listed some common labels, you can add or remove as needed

In Dingtalk app, the system will automatically remove empty rendered lines (due to non-existent labels), so you can configure freely

WeCom App

You need to configure Integration Center-Instant Message-WeCom integration first to send message cards. If custom content is not set, the system default template will be used, rendering only common label information:

We've listed some common labels, you can add or remove as needed

In WeCom app, the system will automatically remove empty rendered lines (due to non-existent labels), so you can configure freely

As shown below:

Note: WeCom limits card length. In the template rendering area, you can render no more than 8 lines of content. Content beyond 8 lines will be hidden

Slack App

You need to configure Integration Center-Instant Message-Slack integration first to send message cards. If custom content is not set, the system default template will be used, rendering only common label information:

As shown below:

If you want to display only key label information, you can refer to the code segment below:

We've listed some common labels, you can add or remove as needed

Messages can be around 15000 characters long, content beyond this will be truncated

In Slack app, the system will automatically remove empty rendered lines (due to non-existent labels), so you can configure freely

Microsoft Teams App

You need to configure Integration Center-Instant Message-Microsoft Teams integration first to send message cards. If custom content is not set, the system default template will be used, rendering only common label information:

{{if .Description}}**description** :{{toHtml .Labels.body_text .Description}}{{end}}
{{if .Labels.resource}}**resource** : {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
{{range $k, $v := .Labels}}
{{if not (in $k "resource" "body_text" "body_text_with_table")}}**{{$k}}** : {{toHtml $v}}{{end}}{{end}}

As shown below:

If you want to display only key label information, you can refer to the code segment below:

We've listed some common labels, you can add or remove as needed

Messages can be around 28KB in size, content beyond this will result in an error

In Microsoft Teams app, the system will automatically remove empty rendered lines (due to non-existent labels), so you can configure freely

{{if (index .Labels "resource")}}**resource**：{{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}
{{if (index .Labels "metric")}}**metric**：{{index .Labels "metric"}}{{end}}
{{if (index .Labels "prom_ql")}}**prom_ql**：{{toHtml (index .Labels "prom_ql")}}{{end}}
{{if (index .Labels "trigger_value")}}**trigger_value**：{{index .Labels "trigger_value"}}{{end}}
{{if (index .Labels "host_ql")}}**host_ql**：{{index .Labels "host_ql"}}{{end}}
{{if (index .Labels "region")}}**region**：{{index .Labels "region"}}{{end}}
{{if (index .Labels "cluster")}}**cluster**：{{index .Labels "cluster"}}{{end}}
{{if (index .Labels "business")}}**business**：{{index .Labels "business"}}{{end}}
{{if (index .Labels "service")}}**service**：{{index .Labels "service"}}{{end}}
{{if (index .Labels "env")}}**env**：{{index .Labels "env"}}{{end}}
{{if (index .Labels "type")}}**type**：{{index .Labels "type"}}{{end}}
{{if (index .Labels "topic")}}**topic**：{{index .Labels "topic"}}{{end}}
{{if (index .Labels "cpu")}}**cpu**：{{index .Labels "cpu"}}{{end}}
{{if (index .Labels "device")}}**device**：{{index .Labels "device"}}{{end}}
{{if (index .Labels "path")}}**path**：{{index .Labels "path"}}{{end}}
{{if (index .Labels "fstype")}}**fstype**：{{index .Labels "fstype"}}{{end}}
{{if (index .Labels "name")}}**name**：{{index .Labels "name"}}{{end}}
{{if (index .Labels "mode")}}**mode**：{{index .Labels "mode"}}{{end}}
{{if (index .Labels "runbook_url")}}**runbook_url**：{{index .Labels "runbook_url"}}{{end}}

Feishu/Lark Bot

Feishu/Lark bot supports message cards, rich text, and plain text formats. The default template is in message card format.

The msg_type field is required for message cards and rich text, otherwise it will be sent as plain text format

The maximum message length is 4000 bytes, content exceeding this limit will be truncated

If no custom content is set, the system default template will be used to display key information:

Message Card
msg_type is required, value should be interactive

{
  "msg_type": "interactive",
  "card": {
    "config": {
      "wide_screen_mode": true,
      "enable_forward": true
    },
    "header": {
      "template": "{{if eq .IncidentSeverity "Critical"}}red{{else if eq .IncidentSeverity "Warning"}}orange{{else}}yellow{{end}}",
      "title": {
        "content": "{{fireReason .}}INC #{{.Num}} {{toHtml .Title}}",
        "tag": "plain_text"
      }
    },
    "elements": [{
      "tag": "div",
      "fields": [{
          "text": {
            "tag": "lark_md",
            "content": "**🏢 Channel:**{{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}"
          }
        },
        {
          "text": {
            "tag": "lark_md",
            "content": "**{{if eq .IncidentSeverity "Critical"}}🔴{{else if eq .IncidentSeverity "Warning"}}⚠️{{else}}ℹ️{{end}} Severity:**{{.IncidentSeverity}}"
          }
        },
        {
          "text": {
            "tag": "lark_md",
            "content": "**⏰ Triggered at:**{{date "2006-01-02 15:04:05" .StartTime}}{{if gt .AlertCnt 1}}"
          }
        },
        {
          "text": {
            "tag": "lark_md",
            "content": "**🔔 Grouped alerts:**{{.AlertCnt}} {{end}}{{if .Labels.resource}}"
          }
        },
        {
          "tag": "div",
          "text": {
            "tag": "lark_md",
            "content": "**📌 Alert targets:**{{toHtml (joinAlertLabels . "resource" ",")}} {{end}}{{if .Description}}"
          }
        },
        {
          "tag": "div",
          "text": {
            "tag": "lark_md",
            "content": "**🔍 Description:**{{.Description}}{{end}}{{if gt (len .Responders) 0}}"
          }
        },
        {
          "tag": "div",
          "text": {
            "tag": "lark_md",
            "content": "**👨‍💻 Responders:**{{range .Responders}}@{{.PersonName}} {{end}}{{end}}"
          }
        }
      ]
    },
    {
      "tag": "hr"
    },
    {
      "tag": "action",
      "actions": [{
          "tag": "button",
          "text": {
            "tag": "plain_text",
            "content": "Details"
          },
          "type": "primary",
          "url": "{{.DetailUrl}}"
        },
        {
          "tag": "button",
          "text": {
            "tag": "plain_text",
            "content": "Acknowledge"
          },
          "type": "primary",
          "url": "{{.DetailUrl}}?ack=1"
        }
      ]
    }]
  }
}

Rich Text
msg_type is required, value should be post

{
    "msg_type": "post",
    "post": {
        "zh_cn": {
            "title": "{{if eq .IncidentSeverity "Critical"}}🔴{{else if eq .IncidentSeverity "Warning"}}⚠️{{else}}ℹ️{{end}} {{fireReason .}}INC #{{.Num}} {{toHtml .Title}}",
            "content": [
                [{
                    "tag": "text",
                    "text": "🏢 "
                }, {
                    "tag": "text",
                    "text": "Channel：",
                    "text_type": "bold"
                }, {
                    "tag": "text",
                    "text": "{{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}\n"
                }],
                [{
                    "tag": "text",
                    "text": "{{if eq .IncidentSeverity "Critical"}}🔴{{else if eq .IncidentSeverity "Warning"}}⚠️{{else}}ℹ️{{end}} "
                }, {
                    "tag": "text",
                    "text": "Severity：",
                    "text_type": "bold"
                }, {
                    "tag": "text",
                    "text": "{{.IncidentSeverity}}\n",
                    "text_type": "{{if eq .IncidentSeverity "Critical"}}bold{{end}}"
                }],
                [{
                    "tag": "text",
                    "text": "⏰ "
                }, {
                    "tag": "text",
                    "text": "Triggered at：",
                    "text_type": "bold"
                }, {
                    "tag": "text",
                    "text": "{{date "2006-01-02 15:04:05" .StartTime}}\n"
                }],
                {{if gt .AlertCnt 1}}[{
                    "tag": "text",
                    "text": "🔔 "
                }, {
                    "tag": "text",
                    "text": "Grouped alerts：",
                    "text_type": "bold"
                }, {
                    "tag": "text",
                    "text": "{{.AlertCnt}}\n"
                }],{{end}}
                {{if .Labels.resource}}[{
                    "tag": "text",
                    "text": "📋 "
                }, {
                    "tag": "text",
                    "text": "Alert targets：",
                    "text_type": "bold"
                }, {
                    "tag": "text",
                    "text": "{{toHtml (joinAlertLabels . "resource" ", ")}}\n"
                }],{{end}}
                {{if .Description}}[{
                    "tag": "text",
                    "text": "📝 "
                }, {
                    "tag": "text",
                    "text": "Description：",
                    "text_type": "bold"
                }, {
                    "tag": "text",
                    "text": "{{toHtml .Description}}\n"
                }],{{end}}
                {{if gt (len .Responders) 0}}[{
                    "tag": "text",
                    "text": "👨‍💻 "
                }, {
                    "tag": "text",
                    "text": "Responders：",
                    "text_type": "bold"
                }, {
                    "tag": "text",
                    "text": "{{range .Responders}}@{{.PersonName}} {{end}}\n"
                }],{{end}}
                [{
                    "tag": "a",
                    "href": "{{.DetailUrl}}",
                    "text": "Details"
                },{
                    "tag": "text",
                    "text": "  "
                },{
                    "tag": "a",
                    "href": "{{.DetailUrl}}?ack=1",
                    "text": "Acknowledge"
                }]
            ]
        }
    }
}

Plain Text

{{fireReason .}}INC #{{.Num}} {{toHtml .Title}}
-----
Channel：{{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}
Severity：{{.IncidentSeverity}}
Triggered at：{{date "2006-01-02 15:04:05" .StartTime}}
Duration：{{ago .StartTime}}{{if gt .AlertCnt 1}}
Grouped alerts：{{.AlertCnt}}{{end}}{{if .Labels.resource}}
Alert targets：{{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}{{if .Description}}
Description：{{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}
Responders：{{range .Responders}}@{{.PersonName}} {{end}}{{end}}
<br/>Details：{{.DetailUrl}}

Dingtalk Bot

Dingtalk bot only supports sending Markdown messages (syntax restrictions).

The maximum message length is 4000 bytes, content exceeding this limit will be truncated

If the text contains  , when rendering, the system will first remove empty lines, then replace with line breaks

If no custom content is set, the system default template will be used to display key information:

{{fireReason .}}INC [#{{.Num}}]({{.DetailUrl}}) {{toHtml .Title}}

---
- Channel: {{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}
- Severity: {{$s := colorSeverity .IncidentSeverity}}{{toHtml $s}}
- Triggered at: {{date "2006-01-02 15:04:05" .StartTime}}
- Duration: {{ago .StartTime}}{{if gt .AlertCnt 1}}
- Grouped alerts: {{.AlertCnt}}{{end}}{{if .Labels.resource}}
- Alert targets: {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}{{if .Description}}
- Description: {{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}
- Responders: {{range .Responders}}@{{.PersonName}} {{end}}{{end}}
---
<br/>[Details]({{.DetailUrl}})|[Acknowledge]({{.DetailUrl}}?ack=1)

WeCom Bot

WeCom bot only supports sending Markdown messages (syntax restrictions).

The maximum message length is 4000 bytes, content exceeding this limit will be truncated

If the text contains  , when rendering, the system will first remove empty lines, then replace with line breaks

If no custom content is set, the system default template will be used to display key information:

{{fireReason .}}**INC [#{{.Num}}]({{.DetailUrl}}) {{toHtml .Title}}**
> Channel: <font color="warning">{{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}</font>
> Severity: <font color="warning">{{.IncidentSeverity}}</font>
> Triggered at: {{date "2006-01-02 15:04:05" .StartTime}}
> Duration: {{ago .StartTime}}{{if gt .AlertCnt 1}}
> Grouped alerts: {{.AlertCnt}}{{end}}{{if .Labels.resource}}
> Alert targets: {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}{{if .Description}}
> Description: {{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}
> Responders: {{range .Responders}}@{{.PersonName}} {{end}}{{end}}
<br/>[Details]({{.DetailUrl}})|[Acknowledge]({{.DetailUrl}}?ack=1)

Telegram Bot

Configure a Telegram service address accessible in mainland China

The maximum message length is 4096 characters, content exceeding this limit will not be sent

If the text contains  , when rendering, the system will first remove empty lines, then replace with line breaks

If no custom content is set, the system default template will be used to display key information:

{{fireReason .}}INC [#{{.Num}}]({{.DetailUrl}}) {{toHtml .Title}}
-----
Channel: {{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}
Severity: {{.IncidentSeverity}}
Triggered at: {{date "2006-01-02 15:04:05" .StartTime}}
Duration: {{ago .StartTime}}{{if gt .AlertCnt 1}}
Grouped alerts: {{.AlertCnt}}{{end}}{{if .Labels.resource}}
Alert targets: {{toHtml (joinAlertLabels . "resource" ", ")}}({{.Labels.resource}}){{end}}{{if .Description}}
Description: {{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}
Responders: {{range .Responders}}@{{.PersonName}} {{end}}{{end}}

<br/>[Details]({{.DetailUrl}})|[Acknowledge]({{.DetailUrl}}?ack=1)

Slack Bot

Messages can be approximately 15000 characters long, content exceeding this limit will be truncated

If the text contains  , when rendering, the system will first remove empty lines, then replace with line breaks

If no custom content is set, the system default template will be used to display key information:

{{fireReason .}}INC <{{.DetailUrl}}|#{{.Num}}> {{toHtml .Title}}
-----
Channel: {{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}
Severity: {{.IncidentSeverity}}
Triggered at: {{date "2006-01-02 15:04:05" .StartTime}}
Duration: {{ago .StartTime}}{{if gt .AlertCnt 1}}
Grouped alerts: {{.AlertCnt}}{{end}}{{if .Labels.resource}}
Alert targets: {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}{{if .Description}}
Description: {{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}
Responders: {{range .Responders}}@{{.PersonName}} {{end}}{{end}}
-----
<br/><{{.DetailUrl}}|Details>|<{{.DetailUrl}}?ack=1|Acknowledge>

Zoom Bot

Messages can be approximately 4000 characters long, content exceeding this limit will be truncated

If the text contains  , when rendering, the system will first remove empty lines, then replace with line breaks

Message format follows Zoom message format. The current bot application doesn't support Markdown. For other formats, please refer to the official documentation: https://developers.zoom.us/docs/team-chat-apps/customizing-messages/

If no custom content is set, the system default template will be used to display key information:

{"head": {
    "text": "{{fireReason .}}INC [#{{.Num}}] {{toHtml .Title}}",
    "style": {
      "bold": true,
      "italic": false,
      "color": "{{$s := serverityToColor .IncidentSeverity}}{{toHtml $s}}"
    }
  },
  "body": [
    {
      "type": "message",
      "text": "Channel: {{if .ChannelName}}{{.ChannelName}}{{else}}None{{end}}",
      "style": {
        "bold": false,
        "italic": false
      }
    },
    {
      "type": "message",
      "text": "Severity: {{.IncidentSeverity}}",
      "style": {
        "bold": false,
        "italic": false,
        "color": "{{$s := serverityToColor .IncidentSeverity}}{{toHtml $s}}"
      }
    },
    {
      "type": "message",
      "text": "Duration: {{ago .StartTime}}{{if gt .AlertCnt 1}}",
      "style": {
        "bold": false,
        "italic": false
      }
    },
    {
      "type": "message",
      "text": "Grouped alerts: {{.AlertCnt}}{{end}}{{if .Labels.resource}}",
      "style": {
        "bold": false,
        "italic": false
      }
    },
    {
        "type": "message",
        "text": "Alert targets: {{.Labels.resource}}{{end}}{{if .Description}}",
        "style": {
          "bold": false,
          "italic": false
        }
      },
    {
      "type": "message",
      "text": "Description: {{toHtml .Description}}{{end}}{{if gt (len .Responders) 0}}",
      "style": {
        "bold": false,
        "italic": false
      }
    },
    {
      "type": "message",
      "text": "Responders: {{range .Responders}}@{{.PersonName}}{{end}}{{end}}",
      "style": {
        "bold": false,
        "italic": false
      }
    },
    {
        "type": "message",
        "text": "View Details",
        "link": "{{.DetailUrl}}{{if .IsFlapping}}"
    },
    {
      "type": "message",
      "text": "Note: The current incident status is changing frequently. Notifications will be suppressed for {{.Flapping.MuteMinutes}} minutes. Please optimize your alert policy.{{end}}{{if .IsInStorm}}",
      "style": {
        "bold": true,
        "italic": false
      }
    },
    {
      "type": "message",
      "text": "Note: The current incident has grouped {{.AlertCnt}} alerts, triggering an alert storm. Please handle with urgency!{{end}}",
      "style": {
        "bold": true,
        "italic": false
      }
    }
  ]
}

Templates

When Are Templates Used?#

How to Configure Notification Templates?#

Configure Notification Templates#

Use Notification Templates#

What Variables Can I Reference?#

Common Questions#

Feishu/Lark App#

Dingtalk App#

WeCom App#

Slack App#

Microsoft Teams App#

Feishu/Lark Bot#

Dingtalk Bot#

WeCom Bot#

Telegram Bot#

Slack Bot#

Zoom Bot#

SMS#

Email#

When Are Templates Used?

How to Configure Notification Templates?

Configure Notification Templates

Use Notification Templates

What Variables Can I Reference?

Common Questions

Feishu/Lark App

Dingtalk App

WeCom App

Slack App

Microsoft Teams App

Feishu/Lark Bot

Dingtalk Bot

WeCom Bot

Telegram Bot

Slack Bot

Zoom Bot

SMS

Email