multiline cri parser fails to parse timestamp

[wengyao04]

Bug Report

Describe the bug

Hi, we use builtin multiline parser cri in our tail plugin like

input.conf: |
    [INPUT]
      Name             tail
      Tag              kube.*
      Path             /var/log/containers/*.log
      multiline.parser cri
      DB               /var/log/flb_kube.db
      Mem_Buf_Limit    5MB
      Skip_Long_Lines  On
      Refresh_Interval 10

But we see error in

{"stream":"stderr","log":"[2022/03/07 18:30:02] [ warn] [parser:_ml_cri] invalid time format %Y-%m-%dT%H:%M:%S.%L%z for '2022-03-07T18:29:56.454636802Z'"}

Not quite sure what 2022-03-07T18:29:56.454636802Z is invalid time format.

To Reproduce

• Rubular link if applicable:
• Example log message if applicable:

{"log":"YOUR LOG MESSAGE HERE","stream":"stdout","time":"2018-06-11T14:37:30.681701731Z"}

• Steps to reproduce the problem:

Expected behavior

Screenshots

Your Environment

• Version used:
• Configuration:
• Environment name and version (e.g. Kubernetes? What version?):
• Server type and version:
• Operating System and version:
• Filters and plugins:

Additional context

[wengyao04]

Hi Do we have a timeline for #5078 ? Is it ready to be merged and create a new release ? Thanks !!

[wengyao04]

Or do we have any temporary solution for parsing cri multiline log ?

[Antiarchitect]

Experiencing the same problem. New release with #5078 is desirable.

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.