Memory and CPU state keyed by connectionId instead of nodeId
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend, observability
Research direction
Trace the frontend memory and CPU metrics state from the metrics server response, focusing on where connectionId is used as the key. Compare that handling with the existing hot keys, big keys, command logs, and monitor state, then verify that two database connections to one node share a single nodeId-keyed copy.
Written by the indexing model from the issue text.
Description
Description
Memory and CPU usage data is fetched from the metrics server (which is keyed by nodeId ). However, the server sends it back to the frontend tagged with connectionId, and the frontend stores it per-connection.
This means if two connections exist to the same node on different databases, they each store a duplicate copy of the same memory/CPU data. It's also inconsistent with how hot keys, big keys, command logs, and monitor are stored (by clusterId or nodeId).
Expected
Memory and CPU state should be keyed by nodeId to match the other metrics features and reflect that this data is node-level, not database-level.
Impact
Duplicate data in state for multi-db connections to the same node. Also a conceptual inconsistency that makes the codebase harder to reason about for new contributors.
- Dominant language
- TypeScript
- Stars
- 143
- Forks
- 29
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 18
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.
More from valkey-io/valkey-admin
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
valkey-io/valkey-admin#518 ·
-
area/server
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
valkey-io/valkey-admin#462 ·
-
area/frontend bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
valkey-io/valkey-admin#442 ·
-
area/frontend enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
valkey-io/valkey-admin#408 ·
-
area/frontend area/server enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
valkey-io/valkey-admin#402 · 1 reaction ·
All issues in valkey-io/valkey-admin
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100