Dashboard Clarity and Organizational Improvements

[quinkirsten]

Problem

The dashboard is fairly clear, but could be tested on outside users for feedback. The main issue that I can spot currently is that some functionality isn't as intuitively labeled and organized as it could be. For example, clicking between cpu usage and memory usage in the heat map changes the other graph displays, while selecting latency (or changing the time window) does not affect anything outside of the heat map. I believe these things would be clear to most users, but might require a learning curve for some, especially those new to Kubernetes.

Solution

As mentioned above, he dashboard is fairly robust as is, but there are several areas for improvement, including:

• Variable titles for the metrics and request/limit graphs that change based on whether cpu usage, memory usage, or latency is selected in the heat map
• More concise labels - making it clear which buttons affect which graphs
• Adding a legend to the pod heat map
• Better pod organization in the heat map, or making it clear how the pods are sorted by default, so that the user doesn't have to sort manually or hover over all pods to find the one they are looking for.

Additional information

No response

👨‍👧‍👦 Contributing

• 🙋‍♂️ Yes, I'd love to make a PR to implement this feature!