Alternate Grafana dashboard better aiding incident resolution

[sagikazarmark]

Describe the solution you'd like
The current dashboard is packed with information that provides a good overview of what's going on, but IMO less useful during an incident. I'm working on an alternate dashboard for that purpose.

What is the added value?
When trying to figure out the root cause of the incident, engineers need the most relevant information at hand. Sure, higher latency is a problem, but it's probably not the root cause of an incident. Failing provider requests are probably a better culprit.

By prioritizing the most important information on the dashboard, the engineer working on an incident will likely determine the root cause quicker.

Give us examples of the outcome

Some information I'd like to see on such a dashboard:

• Number of secret stores (w/ failing validation)
• List of failing secret stores? (cardinality?)
• Provider API call error rates
• Number of failed secrets
• Any other that helps determining whether ESO is the culprit in an incident and if so, how