redpanda-data / redpanda-data/redpanda
schema-registry: provide additional metrics
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.6k
- Forks
- 792
- PR merge metrics
- No merged PRs in 30d
Description
Who is this for and what problem do they have today?
Currently the available metrics in schema registry allow to track request count and latency only. To better understand the usage patterns, it would be important to have additional metrics exported by Redpanda:
- Gauges of:
- Subject count
- Version count
- Schema count
- Schema size
- Histogram of:
- Request size
- Response size
What are the success criteria?
Have Redpanda emit those metrics.
Why is solving this problem impactful?
We want to base infra decisions on data.
JIRA Link: CORE-3072
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 Redpanda's schema registry metrics implementation and the existing request-count and latency metrics. Trace how schema registry requests are measured, then define the gauge and histogram coverage from the issue; done means Redpanda emits subject, version, schema, schema-size, request-size, and response-size metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100