[BUILD-1153] Team dashboards PoC Created: 11/Oct/23  Updated: 06/Feb/24  Resolved: 03/Jan/24

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PNG File image-20220310-084543-1536x803.png    
Issue Links:
relation
supersession
supersedes BUILD-844 Provide teams with new wallboards Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
BUILD-1155 Pick a stack Sub-task Closed Maxime Michel  
BUILD-1154 Expose information not available othe... Sub-task Closed Maxime Michel  
BUILD-1177 Make API self-explanatory Sub-task To Do  
BUILD-1184 Store the configuration in Terraform Sub-task To Do  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

For some time now we have been willing to come up with a replacement to the team dashboards shown in the offices such as: https://dev.magnolia-cms.com/w/?team=bs1

The principle ideas being floated have been:

  • ability to connect to multiple services easily (AWS, Jenkins, Jira, but also Sonar, Notion, Bitbucket, etc.)
  • low barrier to entry: we don't want Foundation to have to write/maintain a framework for this, nor do we want the teams to have to write a lot of code to create/update their dashboards
  • ability to define a team's green/red health for the day based on all the data, the dashboards would be used in the team's standups to monitor for abnormalities
  • the connection to the services should be done in a way that is safe, in other words a team should be comfortable connecting the service even to an AWS account that runs production services

Some ideas we'd like to show on such dashboards:

  • AWS costs
  • status of key Jenkins builds
  • SOC2 unapproved tickets
  • Renovate activity
  • production services availability
  • incoming untriaged support tickets
  • SonarQube/Cloud metrics
  • CVE scans
  • assigned security tickets (replacement to #security bot)
  • open PRs (do they linger?)
  • testing trends (shakiness, tests added/disabled, etc.)
    • disabled tests: by searching the code or looking up tickets?

Generated at Sun Feb 11 23:48:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.