Also, I am partially colorblind (deuteranopia), like more than 1% of men. It would be good if you could choose a color palette respecting the different colorblindness, or at least giving the change for it, to just to allow choosing the colors ourselves.

Hi Prachi - Good feedback. We are evaluating how we can improve the election bars in metrics in the latter half of 2020.

The atlas metrics show node election statuses in colors - red/orange and brown. When there are multiple re-elections in a short period of time, these all merge together making it hard to decipher the order of occurrence - especially the near overlap of orange and brown Having vivid/contrasting colors should make debugging easier. It would be helpful if some aspect about the x-axis would tell you what status the node was in at a given time. For example: the x-axis is also that color from time X to time Y, and then the node was demoted/down and the axis turns to the appropriate color until time Z when the status changes again.

We just had a major outage that appears to be at GCP's networking layer. The only indication in Atlas' UI that anything was wrong was this yellow warning icon, however there was no explanation about what it meant. This was what MongoDB support explained it meant: "The warning signs typically mean that the most recent ping to the cluster did not respond but the vm is not showing as down or offline from the cloud provider. " When asked about where in the UI I could find this information they replied that there was nowhere and that I should come here and open a request so here it is: make sure that for whenever the yellow warning icon is triggered, I can find out why it was triggered. If that's not possible, there is no point in showing a warning icon.

Hey Joanna! This is a great idea, and definitely one that could provide a lot of value to users. Due to the nuances that the yellow exclamation icon encompasses, we've spent a lot of time thinking about what information to include in the tooltip: what if the yellow warning icon represents a transient state which has already triggered Atlas' automatic self-healing? In such a situation where a user does not have to intervene, how would you prefer the message be presented?

Had this yesterday at a workshop at IBM and the student was looking at atlas for the first time. The yellow warning created doubts that everything was okay, even though the cluster was responding, there was no way to know why the primary was showing a warning. I believe that adding a tooltip would improve the UX.