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

Finer grained log export capabilities

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%

    Description

      1. Proposed title of this feature request

      Finer grained log export capabilities 

      1. What is the nature and description of the request

      Currently OpenShift assigns log to one of three categories: application, infrastructure, or audit. All logs within a category can be exported to external log storage/processing systems. However it is not possible to control which log files within a category are exported. 

      The customer would like to continuously export log files to an external log processing platform for analysis (e.g. troubleshooting). However they may not want to export all logs to a single log processing platform, e.g. due to storage space or processing capacity limits. 

      The customer would like the ability to export only a subset of the logs within a particular category (application, infrastructure, audit) and to be able to export different subsets of logs to different external systems. 

      E.g. export logs from application pods A and B to destination X, logs from application pod C to destination Y, logs from infrastructure pod M to destination Z, etc. 

      This would allow the customer to only have to continuously export the logs that they are most interested in, leaving the remaining logs present on the cluster but not exported to any external system. 

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

      The customer may be using a log storage/processing platform that is not able to store all the logs generated within a single OpenShift log category (application, infrastructure or audit). For example in a large Radio Access Network (RAN) deployment, the customer’s log storage/processing platform could be collecting logs from hundreds or thousands of OpenShift clusters. 

      The customer may have different log storage/processing platforms for different purposes, e.g. for troubleshooting different parts of their workload and it is not efficient for example to export all application logs to a log storage/processing platform if only the logs belonging to a subset of the applications pods will be processed. 

      1. List any affected packages or components

      TBD 

      Attachments

        Activity

          People

            jamparke@redhat.com Jamie Parker
            bnivenje@redhat.com Ben Niven-Jenkins
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: