You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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?
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
The text was updated successfully, but these errors were encountered: