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

API for monitoring the visibility receive workflow

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

Details

    • Feature
    • Must have
    • PI16
    • COM SDP SW
    • None
    • Data Processing
    • Hide

      When executing an observation that captures visibility data, an operator (AIV engineer, commissioning scientist) should be able to follow the status of the running receive workflow via a number of monitoring dashboards enabled by a set of APIs exposing this information in a way that is suitable for consumption in Taranta

      Show
      When executing an observation that captures visibility data, an operator (AIV engineer, commissioning scientist) should be able to follow the status of the running receive workflow via a number of monitoring dashboards enabled by a set of APIs exposing this information in a way that is suitable for consumption in Taranta
    • Hide
      • Set of Tango attributes published that enable the development of GUIs for monitoring the status of the "visibility receives" workflow, including but not limited to:
        • The state progress of the workflow/processing script
        • The current processing block and scan IDs being executed
        • Simple statistics about the amount of data ingested and error rates on the SPEAD stream.
      • Update the visibility QA data model to include meta-data for plot labelling in QA displays
      Show
      Set of Tango attributes published that enable the development of GUIs for monitoring the status of the "visibility receives" workflow, including but not limited to: The state progress of the workflow/processing script The current processing block and scan IDs being executed Simple statistics about the amount of data ingested and error rates on the SPEAD stream. Update the visibility QA data model to include meta-data for plot labelling in QA displays
    • Intra Program
    • 3
    • 3
    • 0

    • Use Case USE-22 Operate and Monitor Telescope

      Use Case USE-3 SDP: Configure and execute visibility receive workflow

    • Sub-system Version REL-191 SDP 0.13.0

    • Team_NALEDI
    • Sprint 5
    • Hide

      Pulled workflow stats from visibility receive, and pulledthese into Kafka.
      Workflow statistics
      https://gitlab.com/ska-telescope/sdp/ska-sdp-integration/-/merge_requests/69
      Stats were made available as TANGO attributes.
      Tango device exposure of metrics:
      https://gitlab.com/ska-telescope/sdp/ska-sdp-qa-data-api/-/merge_requests/28
      Tango device integration:
      https://gitlab.com/ska-telescope/sdp/ska-sdp-integration/-/merge_requests/109

      These are displayed on the QA display.

      Show
      Pulled workflow stats from visibility receive, and pulledthese into Kafka. Workflow statistics https://gitlab.com/ska-telescope/sdp/ska-sdp-integration/-/merge_requests/69 Stats were made available as TANGO attributes. Tango device exposure of metrics: https://gitlab.com/ska-telescope/sdp/ska-sdp-qa-data-api/-/merge_requests/28 Tango device integration: https://gitlab.com/ska-telescope/sdp/ska-sdp-integration/-/merge_requests/109 These are displayed on the QA display.
    • 17.3
    • Stories Completed, Integrated, BDD Testing Passes (no errors), Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI24 - UNCOVERED

    • DP-SDP: G1 SOL: G1

    Description

      Introduction

      For the development of GUIs for monitoring SDP visibility receive (Taranta, custom QA displays etc) frontend developers will need APIs to obtain information relating to the status, health, and progress of this workflow.

      This is a continuation & clone of SP-2554 so links Naledi stories related to this previous enabler.

      Who?

      • UI developers: SDP developer, TMC developer

      What?

      • API that publishes status, progress, and metrics to allow a developer to build UIs (Taranta and custom QA displays) for monitoring the AA0.5 SDP visibility receive workflow 

      Why?

      See benefit hypothesis.

      Attachments

        Issue Links

          Child Of

          Capability - SAFe program capability SS-103 Archiving and visualising engineering parameters with the EDA

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          clones

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-2554 API for monitoring the visibility receive workflow

          • 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.
          • Done
          Is delivered by

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-191 SDP 0.13.0

          • Released
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                m.ashdown Ashdown, Mark
                b.mort Mort, Ben
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete619.0
                  Total619.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel