作者:风雪漫天2702934714_713 | 来源:互联网 | 2023-05-18 07:48
目录前言1.安装monitor2.安装prometheus-webhook-dingtalk2.1配置钉钉告警配置文件2.2创建钉钉告警模板2.3创建dingtalkcon
目录
前言
1. 安装monitor
2. 安装prometheus-webhook-dingtalk
2.1 配置钉钉告警配置文件
2.2 创建钉钉告警模板
2.3 创建dingtalk configmap配置文件
2.4 安装dingtalk
2.5 dingtalk调用方法
3. 配置告警
3.1 配置告警接收者
3.2 配置路由默认告警接收者
4. 测试
前言
参考RancherLabs 文章: ( Rancher2.6全新Monitoring快速入门_RancherLabs的博客-CSDN博客
对rancher monitor使用过程中的配置讲解补充,补充了alertmanger发送钉钉告警的实现过程,通过安装dingtalk插件完成钉钉机器人告警推送,详细如下
1. 安装monitor
集群-集群工具Monitoring
![](https://img3.php1.cn/3cdc5/6447/525/2fcc10db6e98f21d.png)
根据实际需求修改部署要求:如持久化,数据保存时长等
![](https://img3.php1.cn/3cdc5/6447/525/1eedfa74b740238c.png)
![](https://img3.php1.cn/3cdc5/6447/525/1718b916053dcfb6.png)
![](https://img3.php1.cn/3cdc5/6447/525/7118cadda04351eb.png)
安装完毕后可在: 集群-监控,查看仪表盘
分别可查看alertmanger、grafana和prometheus web界面
![](https://img3.php1.cn/3cdc5/6447/525/bdc52b58b889ba85.png)
2. 安装prometheus-webhook-dingtalk
2.1 配置钉钉告警配置文件
注意:先创建钉钉机器人,安全验证配置secret,用于下面的配置文件中
创建dingtalk config.yml
# url和secret改为自己的机器人webhook地址和secret
templates:- /etc/prometheus-webhook-dingtalk/dingding.tmpl
targets:k8s:url: https://oapi.dingtalk.com/robot/send?access_token="你的钉钉webhook"secret: "你的钉钉webhook secret"message:title: '{{ template "ops.title" . }}'text: '{{ template "ops.content" . }}'
2.2 创建钉钉告警模板
dingding.tmpl
{{ define "__subject" }}
[{{ .Status | toUpper }}{{ if eq .Status "firing" }}:{{ .Alerts.Firing | len }}{{ end }}]
{{ end }}
{{ define "__alert_list" }}{{ range . }}
---[告警程序]: gz-test-k8s [告警级别]: {{ index .Labels.severity }} [告警类型]: {{ index .Labels.alertname }} [故障实例]: {{ index .Labels.instance }} [告警主题]: {{ index .Annotations.summary }}[告警详情]: {{ index .Annotations.description }}[触发时间]: {{ (.StartsAt.Add 28800e9).Format "2006-01-02 15:04:05" }}
{{ end }}{{ end }}
{{ define "__resolved_list" }}{{ range . }}
---[告警程序]: gz-test-k8s[告警级别]: {{ index .Labels.severity }} [告警类型]: {{ index .Labels.alertname }} [故障实例]: {{ index .Labels.instance }} [告警详情]: {{ index .Annotations.description }}[状态]: 恢复正常[触发时间]: {{ (.StartsAt.Add 28800e9).Format "2006-01-02 15:04:05" }} [恢复时间]: {{ (.EndsAt.Add 28800e9).Format "2006-01-02 15:04:05" }}
{{ end }}{{ end }}
{{ define "ops.title" }}
{{ template "__subject" . }}
{{ end }}
{{ define "ops.content" }}
{{ if gt (len .Alerts.Firing) 0 }}
**侦测到{{ .Alerts.Firing | len }}个故障**
{{ template "__alert_list" .Alerts.Firing }}
---
{{ end }}
{{ if gt (len .Alerts.Resolved) 0 }}
**恢复{{ .Alerts.Resolved | len }}个故障**
{{ template "__resolved_list" .Alerts.Resolved }}
{{ end }}
{{ end }}
{{ define "ops.link.title" }}{{ template "ops.title" . }}{{ end }}
{{ define "ops.link.content" }}{{ template "ops.content" . }}{{ end }}
{{ template "ops.title" . }}
{{ template "ops.content" . }}
2.3 创建dingtalk configmap配置文件
将以上的配置文件保存为文件,通过kubectl创建configmap
$ kubectl create configmap dingtalk-cm --from-file=config.yml=config.yml --from-file=dingding.tmpl=dingding.tmpl -n cattle-monitoring-system
$ kubectl get cm dingtalk-cm -n cattle-monitoring-system
NAME DATA AGE
dingtalk-cm 2 87m
2.4 安装dingtalk
部署文件 dingtalk.yaml
apiVersion: v1
kind: Service
metadata:name: dingtalknamespace: cattle-monitoring-system
spec:selector:app: dingtalkports:- name: httpprotocol: TCPport: 8060targetPort: 8060
---
apiVersion: apps/v1
kind: Deployment
metadata:name: dingtalknamespace: cattle-monitoring-systemlabels:app: dingtalk
spec:replicas: 1strategy:rollingUpdate:maxSurge: 25%maxUnavailable: 25%type: RollingUpdateselector:matchLabels:app: dingtalktemplate:metadata:labels:app: dingtalkspec:restartPolicy: "Always"containers:- name: dingtalkimage: timonwong/prometheus-webhook-dingtalkimagePullPolicy: "IfNotPresent"volumeMounts:- name: dingtalk-confmountPath: /etc/prometheus-webhook-dingtalk/resources:limits:cpu: "400m"memory: "500Mi"requests:cpu: "100m"memory: "100Mi"ports:- containerPort: 8060name: httpprotocol: TCP readinessProbe:failureThreshold: 3periodSeconds: 5initialDelaySeconds: 30successThreshold: 1tcpSocket:port: 8060livenessProbe:tcpSocket:port: 8060initialDelaySeconds: 30periodSeconds: 10volumes:- name: dingtalk-confconfigMap:name: dingtalk-cm
部署到命名空间下:cattle-monitoring-system
> kubectl get deployments.apps dingtalk -n cattle-monitoring-system
NAME READY UP-TO-DATE AVAILABLE AGE
dingtalk 1/1 1 1 68m
> kubectl get svc dingtalk -n cattle-monitoring-system
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
dingtalk ClusterIP 10.43.245.38 8060/TCP 69m
2.5 dingtalk调用方法
# 和alertmanager部署在同个命名空间则可以使用以下的方式调用
# http://dingtalk:8060/dingtalk/"你的钉钉webhook名字"/send
# 如配置了k8s的接收者,地址如下
http://dingtalk:8060/dingtalk/k8s/send
3. 配置告警
3.1 配置告警接收者
集群-监控-Alerting-Routes and Receivers-接收者-创建
![](https://img3.php1.cn/3cdc5/6447/525/27750b95b5eb7938.png)
创建一个默认接收者,同时接收邮件和钉钉告警
![](https://img3.php1.cn/3cdc5/6447/525/fdfcfc6c13bc8832.png)
![](https://img3.php1.cn/3cdc5/6447/525/a77a2bce9753bc43.png)
3.2 配置路由默认告警接收者
集群-监控-Alerting-Routes and Receivers-路由
root匹配全部告警规则,不可删除
![](https://img3.php1.cn/3cdc5/6447/525/2684019c0ad1c715.png)
![](https://img3.php1.cn/3cdc5/6447/525/c59a30b8e1e63b2e.png)
4. 测试
rancher monitor安装后,默认配置了针对组件、节点、pod的告警策略,可在 集群-监控-Advanced-PrometheusRule 查看,修改或新增,具体按实际需要
![](https://img3.php1.cn/3cdc5/6447/525/381a6e873b5eeab2.png)
在本配置了接收者和路由后,可以看到当触发告警时,收到对应的邮件通知
![](https://img3.php1.cn/3cdc5/6447/525/05f3f195aa5ecff6.png)
钉钉告警
![](https://img3.php1.cn/3cdc5/6447/525/e86546c32fa31464.png)
觉得有用点个关注吧~欢迎一起讨论