redpanda-data / redpanda-data/observability
Leaderless Partition Count Incorrect in Ops Dashboard
Nobody has claimed this yet.
- Dominant language
- Jsonnet
- Stars
- 52
- Forks
- 12
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 1
Description
I noticed when using the Redpanda Ops dashboard JSON in Grafana that when I had a cluster that listed over 100 leaderless partitions in rpk cluster health output that the widget in the dashboard thought that there were only 3.
I think there is either a bug in the metrics calculation for the widget, or (as was suggested on Slack) that the server is not reporting enough metrics data when partitions are leaderless to calculate the answer correctly.
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
Inspect the Redpanda Ops dashboard JSON in Grafana and compare the widget's leaderless-partition calculation with the count reported by rpk cluster health. Check whether the server exposes enough metrics for leaderless partitions; done means the dashboard accurately displays clusters with more than 100 leaderless partitions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100