Uploaded image for project: 'Observability and Data Analysis Program'
  1. Observability and Data Analysis Program
  2. OBSDA-1048

Runbooks for the collector and Loki alerts

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • Logging 5.8, Logging 5.9, Logging 6.0, Logging 6.1, Logging 6.2
    • PM Logging
    • False
    • None
    • False
    • Not Selected
    • 0

      Proposed title of this feature request

      Runbooks for the collector and Loki alerts

      What is the nature and description of the request?

      The Red Hat Elasticsearch Operator was creating alerts and in those alerts, it was contained a `runbook_url` where basic troubleshooting steps for that alert were present.

      For the alerts generated for the collectors and Loki, it's not visible any troubleshooting documentation in the Red Hat OpenShift docs, but also, it's not visible any `runbook_url`.

      This situation leads to have an alert, but not steps about what's needed to do with that alert.

      Why does the customer need this? (List the business requirements)

      For all the alerts in a system, it should be expected to have a basic steps for troubleshooting those alerts.

      List any affected packages or components.

      Red Hat OpenShift Logging Operator

      Red Hat OpenShift Loki Operator

              jamparke@redhat.com Jamie Parker
              rhn-support-ocasalsa Oscar Casal Sanchez
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: