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

Improve Sippy automation and alerting of potential problems

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • Sippy Automated Alerting
    • False
    • None
    • False
    • Not Selected
    • To Do
    • Impediment
    • 0% To Do, 0% In Progress, 100% Done

      In recent months Sippy has gained the ability to publish metrics and fire alerts to specific parties when problems are detected. Today this capability is mainly used for notifying specific teams who have a vested interest in a particular job when it's pass rate drops below some threshold.

      TRT believes this capability can be significantly expanded to detect and notify us of a number of classes of problems which are difficult for humans to notice, or sometimes are missed simply because nobody happened to look at the right place.

      This related to the 4.Next effort as one of the primary wins here would be to automatically detect problems that are specifically showing up on the build cluster that has been upgraded to the sprintly release.

          1.
          Docs Tracker Sub-task Closed Undefined Unassigned
          2.
          PX Tracker Sub-task Closed Undefined Unassigned
          3.
          QE Tracker Sub-task Closed Undefined Unassigned
          4.
          TE Tracker Sub-task Closed Undefined Unassigned

              Unassigned Unassigned
              rhn-engineering-dgoodwin Devan Goodwin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: