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

Trigger an alert if the clusterLogForwarder is not in "ValidationSuccess" status

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • Logging 6.0, Logging 6.1, Logging 6.2, Logging 6.3
    • Log Collection, PM Logging
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • 0
    • 100% To Do, 0% In Progress, 0% Done
    • Log Collection - Sprint 271

      Proposed title of this feature request

      Trigger an alert if the clusterLogForwarder is not in "ValidationSuccess" status

      What is the nature and description of the request?

      It should be expected that for any reason that if the collector is not working as expected and this is reflected in the "clusterLogForwarder.status.conditions" where the "ValidationSucess" is not "True" and/or it's not permitted to collect some log types for the "serviceAccount" set, then, an alert should be triggered.

      It's common to see how changes are not really working and this is reported to the Red Hat Support, but when checking the "clusterLogforwarder.status.conditions" an error is observed.

      When the error is when creating the first time, this is more evident as the collectors are not working, but when it's a modification, the collectors will continue working with the "old" valid configuration.

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

      Reduce the time to resolve any issue with the configuration making the change more visible.

      List any affected packages or components.

      Logging collector

              cahartma@redhat.com Casey Hartman
              rhn-support-ocasalsa Oscar Casal Sanchez
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: