Bug 1459943

Summary: [RFE] Add a kibana namespace for kibana log fields
Product: OpenShift Container Platform Reporter: Peter Portante <pportant>
Component: RFEAssignee: Jeff Cantrill <jcantril>
Status: CLOSED WONTFIX QA Contact: Xiaoli Tian <xtian>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: aos-bugs, jokerman, mmccomas, pweil, rmeggins
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-12 11:55:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Peter Portante 2017-06-08 16:00:29 UTC
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?

Comment 3 Kirsten Newcomer 2019-06-12 11:55:35 UTC
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.