Uploaded image for project: 'Logging analytics'
  1. Logging analytics
  2. LOG-437

Post Orchestration Audit - Logic to determine which 'Audit Complete' Events to action in POMBA

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Lowest Lowest
    • None
    • None

      As an Ops person I would like POMBA to be triggered in a systematic fashion based upon completion of orchestration events so that I can have up to date information regarding data integrity of instance artifacts vs design model.

       

      General Information

      After the 'orchestration even has been consumed, there will need to be some filtering logic added to determine which events are to trigger a new audit.  This would only apply to MSO triggered events and not to manually triggered VID initiated events.  

       
       
      Value

      Implements systematic initiation of Post orchestration audits in way that avoids repeatedlt re-auditing systems or wasting resources of supporting systems.

       

      Missing information

      • Logic for this filtering is TBD

       

      Success Criteria

      • Event is consumed from DMaaP
      • Applicably algorithm filters out audits that are not required (logic TBD)
      • Process proceeds to completion as per usual

            Unassigned Unassigned
            dkedrosk dkedrosk
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: