Look at alertmanager logs:  journalctl -eu alertmanager (if you are running 
alertmanager under systemd)

Look at the network traffic:  tcpdump -i <interface> -nn -s0 -vA tcp port 
587

Could it be that your target host doesn't accept TLS?

Could it be that your target host has an invalid TLS certificate, or a cert 
which doesn't match the hostname in "########:587"? If you want to keep TLS 
but disable cert verification, then unfortunately there's no global 
smtp_tls_config; as far as I can see you have to set tls_config under the 
email_configs section of every individual receiver.

See:
https://github.com/prometheus/alertmanager/issues/1554
https://github.com/prometheus/alertmanager/pull/1528
https://prometheus.io/docs/alerting/latest/configuration/#email_config

On Wednesday, 15 September 2021 at 19:36:47 UTC+1 [email protected] 
wrote:

> Hi Team,
>
> i had alertmanger configured in my env now i have changed smtp server and 
> now it's showing "Prometheus_Alertmanager_Notification_Failing" error. My 
> alertmanager config is as below.
>
>
> Please help what wrong i am doing
>
>
> global:
> smtp_smarthost: '########:587'
> smtp_from: 'alertmanager@####.com'
> smtp_require_tls: true
> smtp_auth_username: '#######'
> smtp_auth_password: '########'
>

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/d26e0adf-6884-40ac-a937-275e065c6951n%40googlegroups.com.

Reply via email to