-
Notifications
You must be signed in to change notification settings - Fork 147
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
Add header support #71
Comments
hi @ccremer Maybe prometheus libraries need to be updated? Seems there's an accept header being used for scrapes as seen here: Is that something you can look into? |
Hi I realize that I wasn't clear enough about the headers. It's the status-page ( I guess somesomewhere in in the So it's more like the exporter should add the headers to the collection request, not prometheus |
sorry for the late response, I think it doesn't justify allowing all kinds of dynamic headers. We can just add the Accept one for now. Don't hesitate to make a PR, I'll try to get to it earlier! |
Thanks for the response. Cheers |
I know you decided to not have it, but I am giving you the opportunity anyways :p I'm open to modify it |
I think this was solved by #161 |
Many thanks! and sorry for the time it took |
Hello.
Thank you for this project!
I wondered if you could support adding multiple headers via CLI options.
e.g.
apache_exporter --header "Accept: */*" --header "User-Agent: something" --scrape_uri ...
The reason behind this is that we have a modSecurity (WAF) in "Front" of the Apache server and it logs false alerts for missing Accept header. Of course you could add an accept header by default, but it's probably better to make it configurable.
What do you think?
The text was updated successfully, but these errors were encountered: