Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-1397

Allow customer to configure logging excludes via logging api

XMLWordPrintable

    • False
    • False
    • Undefined

      1. Proposed title of this feature request.
        Enable logging excludes for fluentd via logging API
      2. What is the nature and description of the request?
        In OpenShift 3.11 it was possible to use the exclude parameter for the fluentd tail plugin. As the logging API is abstracting the direct usage of fluentd away, it is not possible to use this any more. In case of a debugging situation or an application that is generating a lot of logs users should be able to decide which logs they want to have persisted. One way to achieve this would be to use the tags that fluentd generates and exclude them from forwarding.
      3. Why does the customer need this?
        1. Decreasing the bandwidth and network load that the logging stack generates by letting the user select what needs to be logged.
        2. In debugging scenarios, where it is either not wanted or needed that the complete logging output is sent to the logging backend.
      4. List any affected packages or components.
        1. Fluentd
        2. Logging API

              swilber@redhat.com Shannon Wilber (Inactive)
              rhn-support-tmicheli Tobias Michelis
              Votes:
              3 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: