Closed toya256 closed 8 years ago
I checked the code of multiline parser, and found that it ignores the specifier not to return current time. So it's an issue of multiline parser, not this plugin.
And, I don't recommend to use multiline parser with this plugin. Multiline parser works well for the strongly consistent sequential input (like in_tail
). The input data of this plugin is not.
Thank you for your reply.
This messege field is a raw xml including new lines. So I think should use the multiline format. I tried to directly use a regular expression to the format parameter, but any lines after the first were ignored.
In case of parsing a field including new lines, I'll try to develop a new formatter(or some other solutions like as replacing new lines before parsing).
Writing your own parser plugin looks good idea for your case!
I'll try to develop a new formatter or parser. Thank you so much for your help!
I want to parse messege field to divide into some fields. So I use this parser plugin. But record's time is replaced with fluentd's current time in spite of using 'time_parse no'. Is this bug? Or I have misunderstood? How to keep record's time even after parsing?