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

Retain src-workloads execution statistics in a DB that enables performance monitoring

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

Details

    • Feature
    • Not Assigned
    • None
    • None
    • SRCnet
    • Hide

      An automated way to record (and visualise) information pertaining to src-workload execution within the SRCNet.

      Show
      An automated way to record (and visualise) information pertaining to src-workload execution within the SRCNet.
    • Hide

      AC1: Tasks/workflows are able to publish data about their execution to a database

      AC2: A simple Grafana dashboard shows the key performance statistics (to be defined) for each given run of a task/workflow

      Show
      AC1: Tasks/workflows are able to publish data about their execution to a database AC2: A simple Grafana dashboard shows the key performance statistics (to be defined) for each given run of a task/workflow
    • 1.5
    • 0
    • 22.6

    • PI23 - UNCOVERED

    • tests-compilation

    Description

      We will require a more automated way to record information about src-workloads execution. Currently this is noted manually on Confluence (); this feature is to enable automatic collection of this data. After establishing a new document-store type DB, tasks and workflows can publish events to this DB that describe the key properties of each run, including information about the hardware (where possible), and the run time.

      This data can then be visualised in a dashboard such as Grafana, for easier assessment of SRCNet 0.1 site performances.

      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-4288 Add benchmark metrics into a dashboard

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Implementing

          Structure

            Activity

              People

                b.mort Mort, Ben
                j.collinson Collinson, James
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 1.5

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

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel