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

Ability to modify the verbosity for the infra project logs when forwarding to cluster logging stack

    XMLWordPrintable

Details

    • False
    • False
    • 0
    • 0% 0%
    • Undefined
    • 0

    Description

      1. Proposed title of this feature request
      Ability to modify the verbosity for the infra project logs when forwarding to cluster logging stack

      2. Who is the customer behind the request?

      Account: Zurich Insurance Company LTD (acct #5433376)

      3. What is the nature and description of the request?
      The customer needs an ability within the OpenShift cluster logging stack that infrastructure logs are using a lot of storage because there is no way of decreasing the verbosity of the logs generated by the OpenShift projects. Not even changing the Fluentd <system> configuration solved the issue. Customers need an option to filter out logs or only get important logs stored in the logging stack so that they can effectively troubleshoot errors and also save on storage space by saving only the relevant logs.

      4. Why does the customer need this? (List the business requirements here)
      There are a lot of infrastructure logs whose information is not relevant to the customer and they also consume a lot of storage space. In the event of the occurrence of an error, the customer cannot list out the actual errors causing the issue. It is very hard to troubleshoot and find the root cause.

      5. How would the customer like to achieve this? (List the functional requirements here)
      Customers should be able to specify the verbosity for the infrastructure projects logs in a way supported by Red Hat. For example, being able to do something like this not only for the kubelet but also for all the OCP projects. As a result, users of the OCP platform could gather only the relevant logs for the infrastructure, resulting in troubleshooting the problems easier and faster.

      6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
      No

      7. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
      No

      Attachments

        Issue Links

          Activity

            People

              jamparke@redhat.com Jamie Parker
              rhn-support-mmarkand Mridul Markandey
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: