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

Ability to modify verbosity of logs when forwarding to external log aggregator

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Obsolete
    • Icon: Minor Minor
    • None
    • None
    • Log Collection, PM Logging
    • None
    • False
    • False
    • Undefined

      What is the problem that your customer is facing?

      Customer needs an ability within logging stack to independently change verbosity of infra, application and audit logging when forwarding logs to external system.

      They want configurable verbosity to help control cost of external log aggregation services.

      What is the business impact, if any, if this request will not be made available?

      Many log aggregation services are priced based on how many megabytes of logs are received by the logging service. OpenShift 4 is extremely "chatty". We need the ability to filter-out logs based on the node type and filter-out based on the "severity" of the log entry, and leave unfiltered logs available in the cluster's internal log system (ELK) for a per-configured amount of time.

      What are your expectations for this feature

      Ability to modify verbosity of log sources while forwarding them to external system. May be an environment variable/parameter within clusterlogging CR for log collector (fluentd) in order to modify versbosity of logs.

       

              rh-ee-rfloren Roger Florén
              rhn-support-dkulkarn Devendra Kulkarni (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: