transparency-dev / transparency-dev/tesseract
429 Rate Limits show up as WARNING logs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 37
- Forks
- 18
- Avg merge
- 19h 22m
- Merged PRs (30d)
- 15
Description
These logs aren't necessarily indicative of a bad behaviour, especially when TesseraCT is rate limiting old certificates. Therefore, they shouldn't be flagged as WARNING log entries. This might be a good one to look at while looking into #843.
This is what logs can look like when there's a lot of rate limits, which looks a bit alarming at first sight:
Contributor guide
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
Start by locating the Go code that handles HTTP 429 responses and emits the WARNING logs, then inspect the related rate-limit behavior referenced by issue #843. Done means rate-limited old certificates no longer produce alarming WARNING entries, with existing logging tests or checks updated as needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100