Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-1098

Ensure Critical alerts have complete playbook entries

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major
    • Resolution: Done
    • None
    • Logging 5.1
    • Log Storage
    • None
    • False
    • False
    • NEW
    • NEW
    • Undefined
    • 3
    • Logging (LogExp) - Sprint 200

    Description

      Provide copy/paste commands to issue

      easy to follow checks/next steps (think needing to wake up in the middle of the night to resolve)

       

      Current upstream doc is here: https://github.com/openshift/elasticsearch-operator/blob/master/docs/alerts.md 

       

      (Currently we are focusing on Critical in this task to make this more bite-sized – we will have follow up for warning and info as well)

      Acceptance Criteria:

      • Ensure that any alerts that are marked as critical have proper diagnostic steps and action steps so that an user can resolve the alert
      • Possibly also ensure that our alerts are using the run{{book_url}} variable to point to our playbook location (tbd if this will be upstream or downstream)

      Attachments

        Issue Links

          Activity

            People

              sasagarw@redhat.com Sashank Agarwal (Inactive)
              ewolinet@redhat.com Eric Wolinetz (Inactive)
              Qiaoling Tang Qiaoling Tang
              Qiaoling Tang Qiaoling Tang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: