Why does the fluentd config file filter-kibana-transform.conf so many keys from the original logs? Currently as of a0be43d (https://github.com/openshift/origin-aggregated-logging) in https://github.com/openshift/origin-aggregated-logging/blob/master/fluentd/configs.d/openshift/filter-kibana-transform.conf we have the following: remove_keys req,res,msg,name,level,v,pid,err Why are we removing "req", "res", "name", "level", "v", and "pid"? That seems like valuable metadata that we would want to keep in a Kibana related namespace, no?
See https://github.com/openshift/origin-aggregated-logging/pull/474
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers. Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant. This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.