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

Automate applying symptom labels in BQ job_labels

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • Product / Portfolio Work
    • False
    • Hide

      None

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

      Ref. Symptoms / observations / job analysis feature

      Context: This step focuses on automating the process of applying symptom labels to job runs when they are finished running.
       
      Action Items:

      • Create sippy API endpoint publishing defined symptoms
      • Within the job intake cloud function (LoadJobRunData):
        • Read and briefly cache the defined symptoms and labels from the sippy API (for e.g. 1 minute)
        • For the file being processed, determine if the symptom matches it and create entry appropriately in BQ job_labels

      As much as possible, logic for determining labels and writing them should be located in the sippy codebase (and imported by the cloud function), to facilitate reuse by other tools doing the same things in different contexts.

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

                Created:
                Updated: