Bug 1459943 - [RFE] Add a kibana namespace for kibana log fields
[RFE] Add a kibana namespace for kibana log fields
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE (Show other bugs)
All All
unspecified Severity medium
: ---
: ---
Assigned To: Jeff Cantrill
Xiaoli Tian
Depends On:
  Show dependency treegraph
Reported: 2017-06-08 12:00 EDT by Peter Portante
Modified: 2018-01-25 16:46 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter Portante 2017-06-08 12:00:29 EDT
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?

Note You need to log in before you can comment on or make changes to this bug.