Added response_timeout property to prometheus input plugin #2006
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.
Required for all PRs:
While working with a customer to setup monitoring, leveraging their existing Prometheus endpoints to gather metrics, we were getting numerous timeout errors in the logs. Upon further investigation, the prometheus input plugin has a 3 second timeout hard coded. The issue is that some of the prometheus endpoints were taking much longer than 3 seconds to return all available metrics. We converted this to a configuration property, with a default value of 3 seconds, which ultimately solved the problem.
Since the default is still 3 seconds, this should be a non-breaking change.