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

SDP error handling and propagation

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

Details

    • Data Processing
    • Hide

      Handling and propagating errors in the system is a critical function and currently missing from the MVP.

      Show
      Handling and propagating errors in the system is a critical function and currently missing from the MVP.
    • 3
    • 3
    • 1.667
    • Team_SIM
    • Sprint 4
    • 4.6

    • PI24 - UNCOVERED

    • DP_epic_1 Team_SIM goal2

    Description

      Show that an error / alert / alarm within the SDP can propagate over the Tango Interface with TM.

      Develop interfaces to reset and restart processing (when errors are identified).

       

      Suggestion:

      Propagate error from EE through to the tango device (eg storage write error, SPEAD heaps dropped).

      Simplest option is to have the EE exit with a non zero exit code and capture that via k8s.

      Error provided on the Subarray device.

      (proposed) Objectives:

      An EE that exits with a non zero exit code results in an error in the tango device.

      Stretch: Extract richer details on the failure for the EE.

       

      Attachments

        Issue Links

          Child Of

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SS-5 Evolutionary Prototype/SKAMPI

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Done
          is cloned by

          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-714 SDP error handling and propagation

          • 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.
          • Discarded
          relates to

          Spike - A time limited investigation to get some knowledge SP-687 Harmonize approaches to handling errors and exceptions

          • Done

          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-709 Harmonize approaches to handling errors and exceptions: Followup to SP687

          • Not Assigned - Priority is not assigned yet.
          • Done
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                p.wortmann Wortmann, Peter
                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
                  Complete711.0
                  Total711.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel