Proxy configuration is not used when History is fetched

This issue has been tracked since 2022-07-21.

When using a proxy configuration for an alertmanager, history workers won't use the proxy but try to access the alertmanager directly. This is somewhat similar to #3707

Example configuration:

    interval: 60s
        - name: dev-cbk
          uri: https://prometheus-alertmanager.example.oirg/
          proxy: true
          proxy_url: socks5://service-account-token.interal.svc:80
            insecureSkipVerify: true
     enabled: true
     timeout: 5s
     workers: 3
prymitive wrote this answer on 2022-08-05

History doesn't talk to alertmanager, it talks to Prometheus. There's no alert history in alertmanager.

tolleiv wrote this answer on 2022-08-05

@prymitive - thanks for the clarification, but how would I pass that traffic through a proxy then? The history rewrite configuration also lacks a proxy_urI option.

Would you be open to a PR which adds the "proxy_urI" to the history rewrite rules?

tolleiv wrote this answer on 2022-08-05

Thanks for the quick merge :)

More Details About Repo
Owner Name prymitive
Repo Name karma
Full Name prymitive/karma
Language TypeScript
Created Date 2018-09-09
Updated Date 2023-03-17
Star Count 1921
Watcher Count 33
Fork Count 166
Issue Count 2


Issue Title Created Date Updated Date