Email 普罗米修斯电子邮件通知

我有一个

Prometheus

操作员

运行在

Kubernetes

上，我可以监控我的资源和集群。但我没有收到发出警报的电子邮件通知。我应该怎么做才能收到电子邮件

pod/alertmanager-kube-prometheus-0                         2/2     Running   0          72m
pod/kube-prometheus-exporter-kube-state-86b466d978-sp24r   2/2     Running   0          161m
pod/kube-prometheus-exporter-node-2zjc6                    1/1     Running   0          162m
pod/kube-prometheus-exporter-node-gwxlg                    1/1     Running   0          162m
pod/kube-prometheus-exporter-node-ngc5p                    1/1     Running   0          162m
pod/kube-prometheus-exporter-node-vcrw4                    1/1     Running   0          162m
pod/kube-prometheus-grafana-6c4dffd84d-mfws7               2/2     Running   0          162m
pod/prometheus-kube-prometheus-0                           3/3     Running   1          162m
pod/prometheus-operator-545b59ffc9-tpqs5                   1/1     Running   0          163m

NAME                                          TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
service/alertmanager-operated                 ClusterIP   None             <none>        9093/TCP,6783/TCP   162m
service/kube-prometheus                       NodePort    10.106.17.176    <none>        9090:31984/TCP      162m
service/kube-prometheus-alertmanager          NodePort    10.105.17.59     <none>        9093:30365/TCP      162m
service/kube-prometheus-exporter-kube-state   ClusterIP   10.105.149.175   <none>        80/TCP              162m
service/kube-prometheus-exporter-node         ClusterIP   10.111.234.174   <none>        9100/TCP            162m
service/kube-prometheus-grafana               ClusterIP   10.106.183.201   <none>        80/TCP              162m
service/prometheus-operated                   ClusterIP   None             <none>        9090/TCP            162m

NAME                                           DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/kube-prometheus-exporter-node   4         4         4       4            4           <none>          162m

NAME                                                  READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/kube-prometheus-exporter-kube-state   1/1     1            1           162m
deployment.apps/kube-prometheus-grafana               1/1     1            1           162m
deployment.apps/prometheus-operator                   1/1     1            1           163m

NAME                                                             DESIRED   CURRENT   READY   AGE
replicaset.apps/kube-prometheus-exporter-kube-state-5858d86974   0         0         0       162m
replicaset.apps/kube-prometheus-exporter-kube-state-86b466d978   1         1         1       161m
replicaset.apps/kube-prometheus-grafana-6c4dffd84d               1         1         1       162m
replicaset.apps/prometheus-operator-545b59ffc9                   1         1         1       163m

NAME                                            READY   AGE
statefulset.apps/alertmanager-kube-prometheus   1/1     162m
statefulset.apps/prometheus-kube-prometheus     1/1     162m

我的

AlertManager.yaml

如下所示：

global:
  smtp_smarthost: 'smtp.gmail.com:587'
  smtp_from: 'zok@gmail.com'
  smtp_auth_username: 'zok@gmail.com'
  smtp_auth_password: 'xxxxxx'

templates: 
- '/etc/alertmanager/template/*.tmpl'


route:

  group_by: ['alertname', 'cluster', 'service' , 'severity']

  group_wait: 30s

  group_interval: 5m

  repeat_interval: 1h 

  receiver: email-me

  routes:
  - match_re:
      service: ^(foo1|foo2|baz)$
    receiver: email-me
    routes:
    - match:
        severity: critical
      receiver: email-me
    - match:
        service: files
      receiver: email-me

    - match:
        severity: warning
      receiver: email-me

  - match:
      service: database
    receiver: email-me

    group_by: [alertname, cluster, database]
    routes:
    - match:
        owner: team-X
      receiver: email-me
      continue: true

    - match:
        severity: warning
      receiver: email-me 

    - match:
        severity: front-critical
      receiver: email-me   


receivers:
- name: 'email-me'
  email_configs:
  - to: 'meisam@gmail.com'

- name: 'team-Y-mails'
  email_configs:
  - to: 'meisam@gmail.com

我在

Prometheus

仪表板中的警报列表：

---

查看Alertmanager日志（

kubectl logs Alertmanager-kube-prometheus-0 Alertmanager

）。此外，请查看Alertmanager UI以查看是否收到了警报。哦，看起来你在这里发布了真正的敏感信息……考虑一下，改变你的密码……可以肯定的是，你在Gmail控制面板中授权了不安全的应用程序吗？同样，你可能会陷入一个<代码> SMTPXReavyTLS：Trime< /Cord>参数查看ActReManCanel日志（

kubectl记录alertmanager-kube-prometheus-0 alertmanager

）另外，看一下AdvtManueUI，看看是否收到了警报。哦，看起来你在这里发布了真正的敏感信息……考虑和更改密码……当然，你在Gmail控制面板中授权了不安全的应用程序吗？同样，你可能会陷入一个<代码> SMTPXReavyTLS：Trime< /Cord>参数。

global:
  smtp_smarthost: 'smtp.gmail.com:587'
  smtp_from: 'zok@gmail.com'
  smtp_auth_username: 'zok@gmail.com'
  smtp_auth_password: 'xxxxxx'

templates: 
- '/etc/alertmanager/template/*.tmpl'


route:

  group_by: ['alertname', 'cluster', 'service' , 'severity']

  group_wait: 30s

  group_interval: 5m

  repeat_interval: 1h 

  receiver: email-me

  routes:
  - match_re:
      service: ^(foo1|foo2|baz)$
    receiver: email-me
    routes:
    - match:
        severity: critical
      receiver: email-me
    - match:
        service: files
      receiver: email-me

    - match:
        severity: warning
      receiver: email-me

  - match:
      service: database
    receiver: email-me

    group_by: [alertname, cluster, database]
    routes:
    - match:
        owner: team-X
      receiver: email-me
      continue: true

    - match:
        severity: warning
      receiver: email-me 

    - match:
        severity: front-critical
      receiver: email-me   


receivers:
- name: 'email-me'
  email_configs:
  - to: 'meisam@gmail.com'

- name: 'team-Y-mails'
  email_configs:
  - to: 'meisam@gmail.com