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 scrape_timeout_seconds metric (behind feature flag) #9247
Conversation
In general, do we want to have the feature flag more generic, e.g. extra-scrape-metrics? So we let the door open for #7722 and potentially others. |
I see no issue with |
792e995
to
aaa675f
Compare
let's have #8911 first, because it will be easier to rebase your pull request than that one. |
1d8f237
to
988c522
Compare
988c522
to
267c9bd
Compare
Since we will have other metrics pretty soon, WDYT about changing directly the internal variable names? |
sorry, I did not mean to close it |
Add a new built-in metric `scrape_timeout_seconds` to allow monitoring of the ratio of scrape duration to the scrape timeout. Hide behind a feature flag to avoid additional cardinality by default. Signed-off-by: SuperQ <superq@gmail.com>
267c9bd
to
31f4108
Compare
Thanks! |
…ape target in the same way as Prometheus 2.30 does See prometheus/prometheus#9247
…ape target in the same way as Prometheus 2.30 does See prometheus/prometheus#9247
Add a new built-in metric
scrape_timeout_seconds
to allow monitoringof the ratio of scrape duration to the scrape timeout. Hide behind a
feature flag to avoid additional cardinality by default.
Signed-off-by: SuperQ superq@gmail.com