cmd,collector: add --scrape.timeout to time-bound scrapes #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the exporter runs queries without any time bounds. This means a poorly behaved query will just run for ever. A connection limit on the exporter role should prevent queries from piling up, but query pile up is still something to be concerned about.
Validated by creating this file:
Running with a
--scrape.timeoutof 10s:❯ ./postgres_exporter \ --extend.query-path=timeout_test_queries.yaml \ --scrape.timeout=10s \ --log.level=infocURL-ing:Repeating with a
--scrape.timeoutof 2s does not include thepg_long_query_value❯ curl http://localhost:9187/metrics | grep long_query % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 93091 0 93091 0 0 46352 0 --:--:-- 0:00:02 --:--:-- 46360But does include partial results: