Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-4632

Consolidate Existing Monitoring Dashboards

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • Services
    • Hide

      In last 3 PIs, System team released new series of dashboards and updated the existing ones as demoed in PI Demo and System Demos. The feedback to those dashboards have been:

      • Readability needs to be improved with accessibility in mind
      • Dashboards are not user friendly as there's no easy way to understand what purpose they serve
      • There are duplications which confuses people to where to look
      • Some dashboards are used by multiple level of stakeholders

      To address these issues, System team wants to work on generating purposeful, use-case based dashboards that contributes directly to developer activities with minimum number of dashboards.

      Show
      In last 3 PIs, System team released new series of dashboards and updated the existing ones as demoed in PI Demo and System Demos. The feedback to those dashboards have been: Readability needs to be improved with accessibility in mind Dashboards are not user friendly as there's no easy way to understand what purpose they serve There are duplications which confuses people to where to look Some dashboards are used by multiple level of stakeholders To address these issues, System team wants to work on generating purposeful, use-case based dashboards that contributes directly to developer activities with minimum number of dashboards.
    • Hide
      • There only exists a handful of dashboards for Developers and PO/PMs:
        • Tango Specific Dashboard (no other tango related information should be present in other dashboards)
        • Resource dashboards per deployments/pods
        • Resource dashboards for environments (linked to above one when necessary)
        • CI/CD Dashboards for understanding their usage of pipelines
        • Environment Dashboards to understand their usage for environments
      • High Level panels should be added where necessary to easily compare between different inputs (teams, pipelines, environments, deployments)
      • Admin dashboards needs to be consolidated similarly to the above criteria but thinking of ST as user
      • Dashboards groups needs to be organised with a agreed structure with discussion with users (TMC and OSO teams as users, TBD)
      • Any unused dashboard is deleted
      • User should be able to create/save dashboards
      • Intent/Purpose of each dashboard should be added to each dashboard so that user is informed
      • Tiered approach is chosen (above AC already conforms) so that high level dashboards are for PM, top AIVs, mid levels are for PO, System Testers, low levels are for developers etc.
      • READ: https://grafana.com/docs/grafana/latest/dashboards/build-dashboards/best-practices/?pg=blog&plcmt=body-txt

        • A dashboard should tell a story or answer a question

        • Dashboards should reduce cognitive load, not add to it

      Show
      There only exists a handful of dashboards for Developers and PO/PMs: Tango Specific Dashboard (no other tango related information should be present in other dashboards) Resource dashboards per deployments/pods Resource dashboards for environments (linked to above one when necessary) CI/CD Dashboards for understanding their usage of pipelines Environment Dashboards to understand their usage for environments High Level panels should be added where necessary to easily compare between different inputs (teams, pipelines, environments, deployments) Admin dashboards needs to be consolidated similarly to the above criteria but thinking of ST as user Dashboards groups needs to be organised with a agreed structure with discussion with users (TMC and OSO teams as users, TBD) Any unused dashboard is deleted User should be able to create/save dashboards Intent/Purpose of each dashboard should be added to each dashboard so that user is informed Tiered approach is chosen (above AC already conforms) so that high level dashboards are for PM, top AIVs, mid levels are for PO, System Testers, low levels are for developers etc. READ: https://grafana.com/docs/grafana/latest/dashboards/build-dashboards/best-practices/?pg=blog&plcmt=body-txt A dashboard should tell a story or answer a question Dashboards should reduce cognitive load, not add to it
    • 2
    • 2
    • 0

    • PI25 - UNCOVERED

    • Team_SYSTEM

    Description

      We need to consolidate, improve, trim down and improve the instructions/tooltips on the dashboards to reduce our work in maintaining then and to make them more accessible and easy to navigate for our different stakeholders (us, developers, architects/PM/PO) as a continuation of the work we have done in PI23

       

      This means consolidation of k8s, gitlab and CI/CD dashboards. The rest of the admin level dashboards are outside of this feature due to capacity concerns.

      Attachments

        Issue Links

          relates to

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4618 Improvements to monitoring of products/services deployed to different environments

          • High - Serious problem that could block progress.
          • Program Backlog

          Structure

            Activity

              People

                b.mort Mort, Ben
                U.Yilmaz Yilmaz, Ugur
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete00.0
                  Total00.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel