High-Level Data Dashboard for SLT

[Matt-Alinosn]

Background

After a recent 'event' where we were asked to provide data on an presumed DOS incident, it became clear that while data is available it is not always quickly and easily to expose. We need to create a mechanism to both expose data via a dashboard or another format

Proposed user journey

Ideally I would like us to provide two types of data that will support the needs of our P&A leadership and around the health of the platform.

Example for P&A leadership is - Number of Namespaces, Unique Name Spaces, Those in Production. Then something including average number of actions on our busiest day (say if Tuesdays traditionally see a peak of traffic) or average number of 2xx's, 4xxs and 5xx responses. to help demonstrate the stability of platform.

Approach

Which part of the user docs does this impact

Communicate changes

• [ ] post for #cloud-platform-update
• [ ] Weeknotes item
• [ ] Show the Thing/P&A All Hands/User CoP
• [ ] Announcements channel

Questions / Assumptions

Definition of done

• [ ] readme has been updated
• [ ] user docs have been updated
• [ ] another team member has reviewed
• [ ] smoke tests are green
• [ ] prepare demo for the team

Reference

How to write good user stories