prometheus-msteams: [BUG]Prometheus-msteams does not send alerts to msteams channel via proxy server
- I used prometheus to send alerts to teams via a proxy server but no data is received.
error as follows:
..../IncomingWebhook/e7e0714e1fb808a0589419bb75/21733118-bf94-4772-af1f-38caea159c3: dial tcp 52.98.40.66:443: i/o timeout ..../IncomingWebhook/e7e0363714e1fb808a0589419bb75/21733118-bf94-4772-af1f-38caea159c3: dial tcp 40.100.54.242:443: i/o timeout
-
I installed prometheus-msteams on centos 7 with a binary
-
Please give me some advice, thank you
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 22
Your test shows that you can reach
prometheus-msteams
, butprometheus-msteams
does not seem to reach your webhook URL. Next step would be to check whether you see incoming requests at the proxy.you have to make sure that
alertmanager --> prometheus-msteams
does not use the proxy (which is presumably running on another host?!). If you export http proxy env variables on the linux host, it will also be picked up by Alertmanager. You can setNO_PROXY
env variable for that.Yeah the error is in the alertmanager, not in prometheus-msteams. So it should be:
Between Alertmanager and prometheus-msteams, you shouldn’t require proxy settings, as they seem to run on the same system, don’t they?
You are trying to access prometheus-msteams from Alertmanager using
localhost
. Can you verify that you can reach prometheus-msteams via localhost from Alertmanager? HOw do you run Alertmanager, also as a systemd process?I assume, this is how
config.yaml
looks like?@baraconguyen sorry for being too fast in closing the issue.
Can you describe your infrastructure setup please?