Fluentd JSON logs truncate after 16385 characters- How to concate?

Keywords: ELK - Other - How to - Other
I am very new to Fluentd and need expert support. I have deployed:
repository: bitnami/fluentd
tag: 1.12.1-debian-10-r0
Currently, one of the modules/applications inside my namespaces are configured to generate JSON logs. I see logs in Kibana as JSON format.

But there is the issue of splitting/truncating logs after 16385 characters, and I cannot see full logs trace.
I have tested some of the concat plugins but they don’t give the expected results so far. or maybe I did the wrong implementation of Plugins.

fluentd-inputs.conf: |
  # Get the logs from the containers running in the node
    @type tail
    path /var/log/containers/*.log
    tag kubernetes.*
      @type json
      time_key time
      time_format %Y-%m-%dT%H:%M:%S.%NZ
  # enrich with kubernetes metadata
  <filter kubernetes.**>
    @type kubernetes_metadata
  <filter kubernetes.**>
    @type parser
    key_name log
    reserve_data true
      @type json
  <filter kubernetes.**>
    @type concat
    key log
    stream_identity_key @timestamp
    #multiline_start_regexp /^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2},\d+ .*/
    multiline_start_regexp /^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}.\d{3}
    flush_interval 5

fluentd-output.conf: |
  <match **>
    @type forward
     # Elasticsearch forward
      @type file
      path /opt/bitnami/fluentd/logs/buffers/logs.buffer
      total_limit_size 1024MB
      chunk_limit_size 16MB
      flush_mode interval
      retry_type exponential_backoff
      retry_timeout 30m
      retry_max_interval 30
      overflow_action drop_oldest_chunk
      flush_thread_count 2
      flush_interval 5s
      flush_thread_count 2
      flush_interval 5s
  {{- else }}
  # Send the logs to the standard output
  <match **>
    @type stdout
  {{- end }}

I am not sure but a reason could be that inside fluentd configuration, some Plugins are already used to filter JSON data, and maybe there is a different way to use a new concat plugin. ? or it can be configured in a different way. ?

I am really struggling with this issue for few days. Can you please support me?

Hi @kishorkk91,

We handle issues with our Helm Charts directly in Github. Could you post your question there?



1 Like