parse_aws_alb_log Failing due to new log format

[misterek]

A note for the community

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Problem

AWS is introducing a traceabilty ID to the end of AWS ALB Logs. Current behavior is function call error for "parse_aws_alb_log" at (54:82): Log should be fully consumed: " TID_""

Configuration

No response

Version

0.38

Debug Output

No response

Example Data

No response

Additional Context

No response

References

vectordotdev/vrl#862

[jszwedko]

Thanks for this report @misterek ! I think it is the same as vectordotdev/vrl#852 so I'll close this one as a duplicate (there is also a workaround in that issue). I recognize that this is a severe issue though so we'll try to address it next week.