夜莺-Nightingale
夜莺V6
项目介绍 架构介绍
快速开始 快速开始
黄埔营
安装部署 安装部署
升级
采集器 采集器
使用手册 使用手册
API API
数据库表结构 数据库表结构
FAQ FAQ
开源生态
Prometheus
版权声明
第1章:天降奇兵 第1章:天降奇兵
第2章:探索PromQL 第2章:探索PromQL
第3章:Prometheus告警处理 第3章:Prometheus告警处理
第4章:Exporter详解 第4章:Exporter详解
第5章:数据与可视化 第5章:数据与可视化
第6章:集群与高可用 第6章:集群与高可用
第7章:Prometheus服务发现 第7章:Prometheus服务发现
第8章:监控Kubernetes 第8章:监控Kubernetes
第9章:Prometheus Operator 第9章:Prometheus Operator
参考资料

The basic configuration for alerts mainly involves the basic description of alert information. The configuration is quite simple. This section mainly introduces alert variables and additional tags.

Alert Variables

The variables used here are consistent with those in the notification templates. If you’re not familiar, you can refer to here. Simply fill in the required variable fields in the alert rule name and remarks, and the corresponding values will be automatically mapped to the variables when an alert notification is triggered. As shown below, the ident is added to the alert rule name, while TriggerTime and TriggerValue are added to the alert remarks. You can see the corresponding values in the alert details.

Basic Configuration 001

This is how the filled-in values are displayed. The corresponding values that trigger the alert can be brought into the alert event details.

Basic Configuration 002

Additional Tags

Additional tags can be understood as custom tags set for alert events. These tags can be used in active alerts, historical alerts, and silenced alerts.

In the previous section, an additional tag type=prometheus was set for the alert rule. Let’s see how to use additional tags below.

Silencing Alerts

Use additional tags as filtering criteria.

Basic Configuration 003

Active Alerts

All three types of aggregation rules can quickly filter alert events using additional tags.

Basic Configuration 004

Historical Alerts

Use additional tags as filtering criteria.

Basic Configuration 005

快猫星云 联系方式 快猫星云 联系方式
快猫星云 联系方式
快猫星云 联系方式
快猫星云 联系方式
快猫星云
OpenSource
开源版
Flashcat
Flashcat