Retry backoff on scrape failure to reduce log spam when queries fail?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 363
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
Do you have any opinion on the idea of having exponential back-off on re-trying failed metric scrapes to reduce log-spam in case of problems?
If it's an idea you're open to I can look at cooking up a patch to support it if my initial PoC of this scraper works out.
CloudNative-PG's built-in scraper, which I currently use, doesn't do this either. But log-spam is a real problem with it if there's a mistake in a query. So it's something I'd like to see if I can implement here if I adopt this scraper.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file, test, or entry point; start by locating the failed metric-scrape retry path in the Go exporter and how query errors are logged. Before implementation, clarify the backoff policy and retry behavior; done would mean failed scrapes retry with exponential backoff and reduce repeated log output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql, prometheus
- Domain
- databases, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100