-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support of sending custom header in Alertmanagers in operatorconfig #307
Comments
Sorry, I don't understand... GMP has nothing to do with Cortex. What are you trying to accomplish? |
I am trying to use cortex's alertmanager to push alert to respective channels. |
OK, I'm not familiar with that. Why do you need headers to be able to communicate with it? |
So cortex's alert-manager needs X-Scope-OrgID to be able to authenticate the request and to be able to figure out the tenant. more on this here. |
Hi any updates on this? |
Hi @kartik7153 - IIUC you want the ability to add a custom header to the alert HTTP request going to the configured alertmanager endpoint? |
Yes right. |
At this point in time, Prometheus does not support custom HTTP headers in its config. The idea has been discussed from the scrape side, but was decided against. However, this should be possible through a forwarding proxy in the |
Note - this soon may be possible with prometheus/common#416.. |
I have some issues about this "use a proxy" workaround as the "official solution". Also the "decided against" is actually a very short conversation, not a real discussion with arguments and counter-arguments, just an "I don't think this is the responsibility of the scraper." statement. I have a counter-argument however, I think it IS the responsibility of the scraper to set headers required by the exporter. No third-party man-in-the-middle service should be required just for doing that. Details in prometheus/prometheus#13098. |
Hi,
We are running our cortex and want to use alertmanager for cortex for routing the alerts. I couldn't see support for adding headers in alertmanagers
The text was updated successfully, but these errors were encountered: