分别用了kubesphere3.1.1 和 3.2.1测试告警消息，邮件服务也配置好了，用3.2.1 邮件服务配置“测试发送信息”成功了，但是告警消息里已经有数据了，就是不发邮件，请问是什么问题

做了各种告警策略，都是触发中了，告警消息里也有数据了，就是不发邮件

    4 天 后

    那就是你的发件服务器配置的有问题，测试发送邮件就是为了测试这个的，你没收到就说明配置的服务器发的邮件发不到你的邮箱里

      ZhangFugui

      测试发送邮件，我收到了，但是系统的告警信息收不到，我查了邮箱也没有垃圾邮件

        1.如果你的接收邮箱不存在，测试邮件也会发送成功的，这个是邮件服务器的问题。登录邮箱确认一下是否收到邮件。

        2.看下kubesphere-monitoring-system下的notification-manager-deploy的日志有没有报错。

        3.kubectl get nr -oyaml 把通知配置贴一下

          wanjunlei

          谢谢您的回复

          测试邮件发送成功了，打开邮箱也收到测试邮件了。

          oyaml截图

          我看alertmanger-main日志有些问题

          下面是Alertmanager的配置

          跟这个配置有关系吗smtp_require_tls: true

            wanjunlei

            还想请教您一个问题，困惑我好久了，我实在找不出来哪里不对，请您帮个忙

            目的就是istio-gateway绑定80端口作为，服务的入口，可以实现前端的灰度发布

            我按照下面这篇文章设置istio-gateway，kubesphere3.1.1自带的istio1.6.10是可以的，但是用kubesphere3.2.1自带的istio1.11.2 就不行。请您帮忙给看下

            https://blog.51cto.com/u_14625168/2496291

              5 个月 后

              level=warn ts=2022-06-23T02:34:49.311Z caller=cluster.go:438 component=cluster msg=refresh result=failure addr=109.233.123.47:9094 err=“1 error occurred:\n\t* Failed to join 109.233.123.47: dial tcp 109.233.123.47:9094: i/o timeout\n\n”

              level=warn ts=2022-06-23T02:34:49.321Z caller=cluster.go:438 component=cluster msg=refresh result=failure addr=alertmanager-main-2.alertmanager-operated:9094 err=“1 error occurred:\n\t* Failed to resolve alertmanager-main-2.alertmanager-operated:9094: lookup alertmanager-main-2.alertmanager-operated on 169.254.25.10:53: no such host\n\n”

              level=warn ts=2022-06-23T02:34:54.328Z caller=cluster.go:438 component=cluster msg=refresh result=failure addr=alertmanager-main-0.alertmanager-operated:9094 err=“1 error occurred:\n\t* Failed to resolve alertmanager-main-0.alertmanager-operated:9094: lookup alertmanager-main-0.alertmanager-operated on 169.254.25.10:53: no such host\n\n”

              level=warn ts=2022-06-23T02:35:09.328Z caller=cluster.go:438 component=cluster msg=refresh result=failure addr=alertmanager-main-0.alertmanager-operated:9094 err=“1 error occurred:\n\t* Failed to resolve alertmanager-main-0.alertmanager-operated:9094: lookup alertmanager-main-0.alertmanager-operated on 169.254.25.10:53: no such host\n\n”

              level=warn ts=2022-06-23T02:35:24.327Z caller=cluster.go:438 component=cluster msg=refresh result=failure addr=alertmanager-main-0.alertmanager-operated:9094 err=“1 error occurred:\n\t* Failed to resolve alertmanager-main-0.alertmanager-operated:9094: lookup alertmanager-main-0.alertmanager-operated on 169.254.25.10:53: no such host\n\n”

              level=warn ts=2022-06-23T02:35:24.328Z caller=cluster.go:438 component=cluster msg=refresh result=failure addr=109.233.114.40:9094 err=“1 error occurred:\n\t* Failed to join 109.233.114.40: dial tcp 109.233.114.40:9094: connect: connection refused\n\n”

              level=warn ts=2022-06-23T02:35:49.311Z caller=cluster.go:438 component=cluster msg=refresh result=failure addr=109.233.114.40:9094 err=“1 error occurred:\n\t* Failed to join 109.233.114.40: dial tcp 109.233.114.40:9094: i/o timeout\n\n”

              level=warn ts=2022-06-23T02:36:04.311Z caller=cluster.go:438 component=cluster msg=refresh result=failure addr=109.233.114.40:9094 err="1 error occurred:\n\t* Failed to join 109.233.114.40: dial tcp 109.233.114.40:9094: i/o timeout\n\n