notifivation-manager接入微信报警收不到信息
这个是我的nm配置文件:
apiVersion: notification.kubesphere.io/v1alpha1
kind: NotificationManager
metadata:
name: notification-manager
namespace: kubesphere-monitoring-system
spec:
replicas: 1
resources:
limits:
cpu: 500m
memory: 1Gi
requests:
cpu: 100m
memory: 20Mi
image: kubesphere/notification-manager:v0.6.0
imagePullPolicy: IfNotPresent
serviceAccountName: notification-manager-sa
portName: webhook
defaultConfigSelector:
matchLabels:
type: default
receivers:
tenantKey: user
globalReceiverSelector:
matchLabels:
type: global
tenantReceiverSelector:
matchLabels:
type: tenant
options:
global:
templateFile:
- /etc/notification-manager/template
email:
notificationTimeout: 5
deliveryType: bulk
slack:
notificationTimeout: 5
wechat:
notificationTimeout: 5
webhook:
notificationTimeout: 5
dingtalk:
notificationTimeout: 5
volumeMounts:
- mountPath: /etc/notification-manager/
name: noification-manager-template
volumes:
- configMap:
defaultMode: 420
name: noification-manager-template
name: noification-manager-template
我把Alertmanager服务暴露出来后,网页访问是可以看到我创建/删除cm的报警信息的,说明alertmanager是可以接收到信息,但是nm好像不能接收到报警信息,我按照官网配置了receivers,如下:
"receivers":
- "name": "Default"
- "name": "Watchdog"
- "name": "Critical"
- "name": "prometheus"
"webhook_configs":
- "url": "http://notification-manager-svc.kubesphere-monitoring-system.svc:19093/api/v2/alerts"
- "name": "event"
"webhook_configs":
- "url": "http://notification-manager-svc.kubesphere-monitoring-system.svc:19093/api/v2/alerts"
- "name": "auditing"
"webhook_configs":
- "send_resolved": false
"url": "http://notification-manager-svc.kubesphere-monitoring-system.svc:19093/api/v2/alerts"
# 上面是默认的,下面是我的
- "name": "notification-manager"
"webhook_configs":
- "url": "http://notification-manager-svc.kubesphere-monitoring-system.svc:19093/api/v2/alerts"
同时配置了route,如下:
- "group_interval": "30s"
"match":
"alerttype": "notification-manager"
"receiver": "notification-manager"
请问老师上面的alertmanage发送报警信息给nm的配置正确吗?万分感谢~
WwanjunleiK零S
贴下nm的日志
# kubectl logs notification-manager-deployment-5675dc9d7-8ts8f -n kubesphere-monitoring-system --tail 500
level=info ts=2021-03-11T14:55:40.804736133+08:00 caller=main.go:100 msg="Starting notification manager..." addr=:19093 timeout=5s
level=info ts=2021-03-11T14:55:43.523676264+08:00 caller=config.go:340 msg="Setting up informers successfully"
level=info ts=2021-03-11T14:56:01.080585465+08:00 caller=config.go:679 msg="resource change" op=add type=wechat name=default-wechat-config namespace=kubesphere-monitoring-system
level=info ts=2021-03-11T14:56:01.094736472+08:00 caller=config.go:679 msg="resource change" op=add type=wechat name=global-wechat-receiver namespace=kubesphere-monitoring-system
# kubectl logs notification-manager-operator-dd4c6fd6f-pqtrc -n kubesphere-monitoring-system -c notification-manager-operator --tail 500
2021-03-11T14:55:21.665+0800 INFO controller-runtime.metrics metrics server is starting to listen {"addr": "127.0.0.1:8080"}
2021-03-11T14:55:21.666+0800 INFO setup starting manager
I0311 14:55:21.666557 1 leaderelection.go:242] attempting to acquire leader lease kubesphere-monitoring-system/7b8d27e6.kubesphere.io...
2021-03-11T14:55:21.670+0800 INFO controller-runtime.manager starting metrics server {"path": "/metrics"}
I0311 14:55:38.534004 1 leaderelection.go:252] successfully acquired lease kubesphere-monitoring-system/7b8d27e6.kubesphere.io
2021-03-11T14:55:38.534+0800 DEBUG controller-runtime.manager.events Normal {"object": {"kind":"ConfigMap","namespace":"kubesphere-monitoring-system","name":"7b8d27e6.kubesphere.io","uid":"cee2a831-d2e0-45de-87af-b4813c744676","apiVersion":"v1","resourceVersion":"904756"}, "reason": "LeaderElection", "message": "notification-manager-operator-dd4c6fd6f-pqtrc_e30b19a1-2d0c-4038-a604-3c23f7ea9158 became leader"}
2021-03-11T14:55:38.536+0800 INFO controller-runtime.controller Starting EventSource {"controller": "notificationmanager", "source": "kind source: /, Kind="}
2021-03-11T14:55:38.837+0800 INFO controller-runtime.controller Starting EventSource {"controller": "notificationmanager", "source": "kind source: /, Kind="}
2021-03-11T14:55:38.837+0800 INFO controller-runtime.controller Starting Controller {"controller": "notificationmanager"}
2021-03-11T14:55:38.837+0800 INFO controller-runtime.controller Starting workers {"controller": "notificationmanager", "worker count": 1}
2021-03-11T14:55:38.964+0800 DEBUG controller-runtime.controller Successfully Reconciled {"controller": "notificationmanager", "request": "kubesphere-monitoring-system/notification-manager"}
2021-03-11T14:55:39.159+0800 ERROR controllers.NotificationManager Failed to CreateOrUpdate deployment {"NotificationManager Operator": "kubesphere-monitoring-system/notification-manager", "result": "unchanged", "error": "Operation cannot be fulfilled on deployments.apps \"notification-manager-deployment\": the object has been modified; please apply your changes to the latest version and try again"}
github.com/go-logr/zapr.(*zapLogger).Error
/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
github.com/kubesphere/notification-manager/pkg/controllers.(*NotificationManagerReconciler).Reconcile
/workspace/pkg/controllers/notificationmanager_controller.go:94
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.2/pkg/internal/controller/controller.go:256
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.2/pkg/internal/controller/controller.go:232
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.2/pkg/internal/controller/controller.go:211
k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1
/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:152
k8s.io/apimachinery/pkg/util/wait.JitterUntil
/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:153
k8s.io/apimachinery/pkg/util/wait.Until
/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:88
2021-03-11T14:55:39.160+0800 ERROR controller-runtime.controller Reconciler error {"controller": "notificationmanager", "request": "kubesphere-monitoring-system/notification-manager", "error": "Operation cannot be fulfilled on deployments.apps \"notification-manager-deployment\": the object has been modified; please apply your changes to the latest version and try again"}
github.com/go-logr/zapr.(*zapLogger).Error
/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.2/pkg/internal/controller/controller.go:258
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.2/pkg/internal/controller/controller.go:232
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.2/pkg/internal/controller/controller.go:211
k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1
/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:152
k8s.io/apimachinery/pkg/util/wait.JitterUntil
/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:153
k8s.io/apimachinery/pkg/util/wait.Until
/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:88
2021-03-11T14:55:40.188+0800 DEBUG controller-runtime.controller Successfully Reconciled {"controller": "notificationmanager", "request": "kubesphere-monitoring-system/notification-manager"}
2021-03-11T14:55:41.420+0800 DEBUG controller-runtime.controller Successfully Reconciled {"controller": "notificationmanager", "request": "kubesphere-monitoring-system/notification-manager"}
WwanjunleiK零S
notification manager没收到消息,问题应该是出在am那边,你重启下am,把全部的日志贴下
wanjunlei
我在ui界面重新部署了下alertmanager,日志如下:
# kubectl logs --tail 500 alertmanager-main-0 -n kubesphere-monitoring-system -c alertmanager
level=info ts=2021-03-11T07:58:45.069Z caller=main.go:216 msg="Starting Alertmanager" version="(version=0.21.0, branch=HEAD, revision=4c6c03ebfe21009c546e4d1e9b92c371d67c021d)"
level=info ts=2021-03-11T07:58:45.069Z caller=main.go:217 build_context="(go=go1.14.4, user=root@dee35927357f, date=20200617-08:54:02)"
level=info ts=2021-03-11T07:58:45.477Z caller=coordinator.go:119 component=configuration msg="Loading configuration file" file=/etc/alertmanager/config/alertmanager.yaml
level=info ts=2021-03-11T07:58:45.562Z caller=coordinator.go:131 component=configuration msg="Completed loading of configuration file" file=/etc/alertmanager/config/alertmanager.yaml
level=info ts=2021-03-11T07:58:45.664Z caller=main.go:485 msg=Listening address=:9093
WwanjunleiK零S
https://github.com/kubesphere/notification-manager/tree/release-0.6/pkg/webhook/testdata
这是nm的测试数据,你直接调用http://notification-manager-svc.kubesphere-monitoring-system.svc:19093/api/v2/alerts发送数据试试
WwanjunleiK零S
有没有收到通知?nm的日志贴下
这样是不是说am到nm是没有问题的吧,是nm到微信是不通的?
WwanjunleiK零S
你把notification manager升级到0.7.0试试
WwanjunleiK零S
你确认下日志级别是不是debug
我发现升级nm到0.7时,出现个奇怪的现象:nm能apply创建成功,但是kubectl get pod -n xxx时竟然没有,什么错误信息都没有~
WwanjunleiK零S
看看notification manager operator的日志吧