Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fluentd config to Parse the log field correctly #458

Open
rajivml opened this issue May 13, 2020 · 2 comments
Open

Fluentd config to Parse the log field correctly #458

rajivml opened this issue May 13, 2020 · 2 comments
Labels
type::feature An enhancement to an existing add on or feature

Comments

@rajivml
Copy link

rajivml commented May 13, 2020

With the default fluentd config, the fields like logger, severity, tenant-id, trace-id and all other fields that are part of json log field are all crammed into one big json blob and hence not queriable.

To index these fields correctly so that all the keys which are part of log field which is a json are queriable, we need to modify the fluentd config like this and right now there isn't any mechanism through which we can pass this filter.

Can you guys please add an additional option through which this config is automatically injected at the time of Infra setup so that one additional manual step is avoided

step1:
kubectl -n logging edit configmap fluentdconf
    # Fixes json fields in Elasticsearch
    <filter kubernetes.**>
      @type parser
      format json
      key_name log
      reserve_time true
      reserve_data true
      remove_key_name_field true
      emit_invalid_record_to_error false
    </filter>
step2: change some param like requests or limits so that pods that are under daemonset gets restarted with updated configMap
kubectl -n logging edit ds/fluentd
@marccampbell marccampbell added the type::feature An enhancement to an existing add on or feature label Jun 13, 2020
@emosbaugh
Copy link
Member

It is possible to add a custom fluentdConfPath. This requires a full config be provided.

https://kurl.sh/docs/add-ons/fluentd

@camilamacedo86
Copy link
Contributor

Hi @rajivml and @emosbaugh,

This one is open for a while. Have we here something that we would still needing to do to address this request? Is it something that still relevant or could we close this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::feature An enhancement to an existing add on or feature
Projects
None yet
Development

No branches or pull requests

4 participants