Kuboard can't send email and nail alarm problem is solved

According to the official document, it has been installed and set successfully , Also started a busybox Containers , Let it crash and restart all the time to trigger alarm messages and nail messages . Found unable to receive mail , Also can't receive nail message .

see kuboard / alertmanager-main journal , It can be seen that the email and nailing message send an error .

level=warn ts=2022-05-27T15:32:50.287Z caller=notify.go:723 component=dispatcher receiver=Critical integration=email[0] msg="Notify attempt failed, will retry later" attempts=1 err="'require_tls' is true (default) but \"smtp.exmail.qq.com:465\" does not advertise the STARTTLS extension"
level=error ts=2022-05-27T15:35:07.518Z caller=dispatch.go:310 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="Default/webhook[0]: notify retry canceled due to unrecoverable error after 1 attempts: unexpected status code 404: http://dingtalk:8060/dingtalk/Default-shzdp/send; Default/email[0]: notify retry canceled after 17 attempts: 'require_tls' is true (default) but \"smtp.exmail.qq.com:465\" does not advertise the STARTTLS extension"

Email alert :

I am using QQ Enterprise mailbox , I can't send alarm emails all the time ,smtp.exmail.qq.com:465, After analyzing the error log, it is found that it needs to be closed TLS Options , The problem of unsuccessful email sending is solved .

  Nail alarm :

level=error ts=2022-05-27T15:41:46.569Z caller=dispatch.go:310 component=dispatcher msg="Notify for alerts failed" num_alerts=2 err="Critical/webhook[0]: notify retry canceled due to unrecoverable error after 1 attempts: unexpected status code 404: http://dingtalk:8060/dingtalk/Critical-8p8nz/send"

Nail container service interface is found in the log 404 了 , We are kuboard Find the nail pod, Go in and check the log .

level=info ts=2022-05-27T16:31:50.549Z caller=entry.go:26 component=web http_scheme=http http_proto=HTTP/1.1 http_method=POST remote_addr=100.100.196.227:34048 user_agent=Alertmanager/0.22.2 uri=http://dingtalk:8060/dingtalk/Default-shzdp/send resp_status=404 resp_bytes_length=19 resp_elapsed_ms=0.068677 msg="request complete"
level=warn ts=2022-05-27T16:31:50.549Z caller=dingtalk.go:75 component=web target=Default-shzdp msg="target not found"

Sure enough, there is an error log , Look at the image of this container , Let's find its source code and see what happens .

  stay hub.docker.com Find the image ,timonwong/prometheus-webhook-dingtalk Tags | Docker Hubhttps://hub.docker.com/r/timonwong/prometheus-webhook-dingtalk/tags stay github Find the image source code , Locate the file line you want to report an error .

prometheus-webhook-dingtalk/dingtalk.go at v2.0.0 · timonwong/prometheus-webhook-dingtalk (github.com)https://github.com/timonwong/prometheus-webhook-dingtalk/blob/v2.0.0/web/dingtalk/dingtalk.go 

Let's see readme.md See what this thing is . It is found that the configuration file used by the container , Some parameters for sending messages are configured .

I know the configuration file of the container , We should enter dingtalk Container view the following , Is this file right .

Sure enough, there is this file , Let's check the contents of the file .

  The contents of the document are correct , At this time, we should think , The configuration file is OK , Why does the code say it can't find targets Well ? Preliminary speculation may be that the document did not take effect , The container starts first , Later kuboard The configuration of access_token.

How to solve it ?

restart dingtalk Container group .