Uploaded image for project: 'CoreOS OCP'
  1. CoreOS OCP
  2. COS-3230

Investigate user interaction with pipeline AI

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • CoreOS Coordination - 273
    • 0

      We'll need to investigate the best way to integrate into our existing workflow:

      - Where we investigate failures today?
          - slack
          - matrix
          - GitHub PRs
      - How do we integrate AI into our existing workflow?
          - options:
              - 1. API to interact with model/log detective
              - 2. web front end to supply logs and prompt (like log detective)
              - 3. slack bot that can take commands in replies to notifications about failures
                  - /bot analyze 'dns resolution'
                      - slack bot identifies links from threaded message chain
                      - interacts with thebeast to register logs and failure annotation
                      - open question: does the bot retrieve the logs and upload them or does the bot tell thebeast where to retrieve the logs from?
                  - pros: it's where we are today when we investigate most failures
                  - cons: slack isn't the only place where we investigate failures
              - 4. have jenkins send the logs to the model on failure
                  - DWM: I think jenkins uploading automatically is a future state, i.e. once our model is trained and gives useful analysis we can then automatically submit failures AND potentially take action based on the analysis
      

              jlebon1@redhat.com Jonathan Lebon
              rhn-gps-dmabe Dusty Mabe
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: