cockroachdb / cockroachdb/pebble
Rate limiter saturation & backlog metrics
Closed
A-storage
T-storage
- Dominant language
- Go
- Stars
- 6k
- Forks
- 584
- Avg merge
- 16h 35m
- Merged PRs (30d)
- 5
Description
Export tokens available/used, queued background work (e.g., pending cold-copy backlog), and stall counters; alerting hooks.
Jira issue: PEBBLE-1279
Epic CRDB-48982
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the rate limiter, background cold-copy queue, and existing metrics or alerting entry points in the Pebble codebase. Trace how token usage, pending work, and stalls are represented; done means the requested saturation, backlog, and stall signals are exported with alerting hooks and covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100