Skip to content
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

Consider passing down scrape timeout as header #2508

Closed
brian-brazil opened this Issue Mar 17, 2017 · 7 comments

Comments

Projects
None yet
4 participants
@brian-brazil
Copy link
Member

brian-brazil commented Mar 17, 2017

I'd like to propose passing the scrape timeout down as a header when scraping. For exporters like snmp and blackbox it'd be good if the user didn't have to set timeouts in two places. More generally for expensive exporters, it'd be good to stop querying when the other side has given up. Whether this would ever be exposed to client libraries is a separate question.

This would be something like:

Scrape-Timeout-Seconds: 10.0 
@fabxc

This comment has been minimized.

Copy link
Member

fabxc commented Mar 17, 2017

Why a header?
We should decide for either headers or query params. Given that we also discussed things like label selectors already, query params make the most sense.

@brian-brazil

This comment has been minimized.

Copy link
Member Author

brian-brazil commented Mar 17, 2017

Headers could be automatic, whereas url parameters are currently explicitly configured by the user.

@fabxc

This comment has been minimized.

Copy link
Member

fabxc commented Mar 17, 2017

@brian-brazil

This comment has been minimized.

Copy link
Member Author

brian-brazil commented Mar 17, 2017

It doesn't seem quite as clean to me. It'd be exposing a minor internal detail on places like the /status page.

@grobie

This comment has been minimized.

Copy link
Member

grobie commented Mar 17, 2017

@juliusv

This comment has been minimized.

Copy link
Member

juliusv commented Mar 17, 2017

Agreed on header in this case.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 23, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.