Repository navigation
Add multi-cluster fleet overview with grouping and issue flagging #406
Description
Customers operating at scale (100s–1000s of clusters) need to quickly identify which clusters need attention. Navigating into each cluster individually doesn't scale. A grouped overview with issue indicators enables faster triage and reduces mean-time-to-detection.
Provide a fleet-level overview for teams managing hundreds or thousands of Valkey clusters. The view should support:
- Grouping: organize clusters by environment, region, team, or custom tags
- At-a-glance health: surface which clusters have active issues (high memory, unreachable nodes, slow command spikes) without requiring navigation into each cluster individually
- Early issue flagging: highlight clusters that need attention so DevOps teams can triage quickly across a large fleet
Activity
hogarth-sv commentedon Jul 28, 2026
Related to this, perhaps I'm missing something already workable, it would be very useful to be able to configure multiple clusters from config file mounted in the container.
For each of my environments I have at least two clusters that this would be useful for. Having a single instance per environment (or even nonprod/prod instances with all relevant clusters under each) would be incredibly useful.
ravjotbrar commentedon Jul 28, 2026
Thanks for the suggestion @hogarth-sv and no you're not missing anything. We'll look at implementing something workable as part of this issue.