Filebeat: wrong multiline merging

Elastic Stack Beats
1

I am trying to run filebeat daemonset in Kubernetes cluster. It is expected to honor the multiline log entries and also parse json log entries.

This is the config snippet:

    filebeat.autodiscover:
      providers:
        - type: kubernetes
          node: ${NODE_NAME}
          hints.enabled: true
          hints.default_config:
            type: container
            paths:
              - /var/log/containers/*${data.kubernetes.container.id}.log
            multiline.pattern: '^[0-9]{4}-[0-9]{2}-[0-9]{2}'
            multiline.negate: true
            multiline.match: after
            multiline.max_lines: 50
            multiline.timeout: 3s
    processors:
      - add_cloud_metadata:
      - drop_event:
          when:
            or: 
              - equals:
                  kubernetes.namespace: "kube-system"
              - equals:
                  kubernetes.namespace: "metallb-system"
      - decode_json_fields:
          fields: ["message"]
          process_array: false
          max_depth: 1
          target: ""
          overwrite_keys: true

Everything works as desired except for one issue: some json logs are being merged together when this is not expected:

multiline
multiline1190×514 53.9 KB

Does anybody know how to deal with it?

2

Hey!

Are you sure that your multiline.pattern is correct? I guess that this might cause the issue.

3

Hi Chris,

The multiline.pattern looks good. Moreover it works nice with the actual multiline entries:

multiline-good
multiline-good1502×761 123 KB

Also the issue with wrong merging appears with any value of multiline.pattern. I have tried to fill it with some random letters and the issue persists. The issue disappears only when I completely remove the multiline config.

4

No more thoughts?

5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.