Uploaded image for project: 'OCP Technical Release Team'
  1. OCP Technical Release Team
  2. TRT-2379

Define symptoms for recent incidents

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • Incidents & Support
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None
    • None

      Ref. Symptoms / observations / job analysis feature

      Context: This step involves practically applying the enhanced JAQ dialog to define symptoms based on recent incidents, thereby populating the symptom specification table.
       
      Action Items:

      • Review recent incidents.
      • Use the JAQ dialog to define symptoms for the factors that contributed to these incidents.
        • If they are InfraFailure problems, then of course just have the symptom apply that label - this causes them to disappear from component readiness.
        • Otherwise, create or reuse other labels appropriately, enabling automatically informing viewers when a known symptom is present.

              Unassigned Unassigned
              lmeyer@redhat.com Luke Meyer
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: