redpanda-data / redpanda-data/observability
Per-node (and per-shard?) CPU utilization should be a heatmap
Nobody has claimed this yet.
- Dominant language
- Jsonnet
- Stars
- 52
- Forks
- 12
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 1
Description
Current design is an overall cluster utilization up to 100%. This masks two things:
- Makes it hard to see if one broker is heavily over-utilized/under-utilized
- Makes it hard to understand actual cpu utilization if you don't know the underlying core counts configured for shards.
It would be good to break up the primary cpu utilization gauge into at least a per-broker heat map (and maybe a per-shard one on one of the lesser dashboards, like the ops dashboard, rather than the default).
I think this will help people understand available headroom given that they're likely used to looking at system.cpu from the kernel where this stuff is more easily accessible, especially if coming from another system like Apache Kafka where java utilization == cpu utilization.
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
Start by reviewing the current overall cluster CPU utilization gauge and how the primary dashboard obtains its metrics. Define whether the default view should show a per-broker heatmap and whether a per-shard view belongs on the ops dashboard; done means utilization and available headroom are understandable without knowing shard core counts.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100