Alertmanager: Alertmanager reaching to receivers via proxy (https)

[netvisao]

Is there currently a way for alertmanager to dispatch alert to receivers' endpoints via proxy?

Example: alertmanager dispatching alerts to pagerduty or slack, where in an entreprise environment, the pagerduty or slack endpoints are only reachable through a (http,https) proxy

[netvisao]

func ProxyFromEnvironment does the trick

[poblin-orange]

Hello,
i also need to send slack notification through a corporate proxy.
Im not aware of alertmanager internals. Is there a way to specify http proxy for the slack notification without coding?
thks

[netvisao]

Exporting http_proxy and https_proxy in your shell environment should make
it work.

On Dec 15, 2016 7:11 AM, "Pierre Oblin" [e-mail] wrote:

Hello,
i also need to send slack notification through a corporate proxy.
Im not aware of alertmanager internals. Is there a way to specify http
proxy for the slack notification without coding?
thks

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/alertmanager/issues/554#issuecomment-267313356,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABkqtA6gLkCfydkvb1jbkY6uBGFL2elPks5rIS54gaJpZM4K27ny
.

[brancz]

Just as a warning: the mean to configure Prometheus and the Alertmanager is using config files, environment variables only work unintentionally as the underlying http implementation supports it. Having said that, there is no stability guarantee for environment variables, the option may disappear in any release, possibly without notice. If you wish to have it in a stable way, a patch to allow specifying it in the config would be welcome (not via env variables).

[netvisao]

Except that, right now, there does not seem that configuration files allow
to use a proxy and the only way is via the http{,s}_proxy

On Dec 15, 2016 4:34 PM, "Frederic Branczyk" [e-mail]
wrote:

Just as a warning: the mean to configure Prometheus and the Alertmanager
is using config files, environment variables only work unintentionally as
the underlying http implementation supports it. Having said that, there is
no stability guarantee for environment variables, the option may disappear
in any release, possibly without notice. If you wish to have it in a stable
way, a patch to allow specifying it in the config would be welcome (not via
env variables).

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/alertmanager/issues/554#issuecomment-267450796,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABkqtPWsfklX6SgKz9jVD5D3eKwUggjeks5rIbJygaJpZM4K27ny
.

[brancz]

a patch to allow specifying it in the config would be welcome

[ddewar2k]

Gang, Looking to see if this every resolved. Looking at the code and configuration guide its not obvious that an HTTP proxy can be added to a webhook config. If this is allowed, does anyone have an example configuration snippet.

[jpiper]

@ddewar2k I can see here

https://github.com/prometheus/docs/blob/master/content/docs/alerting/configuration.md

That there's a proxy_url settings under http_config

[azizzoaib786]

based on documentation .. inside alertmanager.yml file, we can define as below:

global:
hipchat_api_url: 'https://company.hipchat.com'
http_config:
proxy_url: 'http://(IP):3128'

[Prabjyot19]

Can anyone please help me with alertmanager.yml config for opsgenie via proxy server ?

[roidelapluie]

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.

[Prabjyot19]

Thanks for the Guidance @roidelapluie