Skip to content

Commit 8019974

Browse files
committed
parser: clarify that multiline parser does not join separate events
Closes: #338 Signed-off-by: Shizuo Fujita <fujita@clear-code.com>
1 parent ab8daeb commit 8019974

1 file changed

Lines changed: 8 additions & 1 deletion

File tree

parser/multiline.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,14 @@ The `multiline` parser plugin parses multiline logs. This plugin is the multilin
44

55
The `multiline` parser parses log with `formatN` and `format_firstline` parameters. `format_firstline` is for detecting the start line of the multiline log. `formatN`, where N's range is \[1..20\], is the list of Regexp format for multiline log.
66

7-
Unlike other parser plugins, this plugin needs special code in input plugin e.g. handle `format_firstline`. So, currently, `in_tail` plugin works with `multiline` but other input plugins do not work with it.
7+
{% hint style='warning' %}
8+
This parser plugin itself does not join multiple lines. The logic to buffer lines and detect the start of each record is implemented in `in_tail`.
9+
10+
* `<parse>` in `in_tail`: works as described in this article.
11+
* `<filter parser>` and other plugins which receive already-split events: cannot join separate events into one record. It can only parse a value which already contains newline characters.
12+
13+
To concatenate multiple events into one record after the input stage, use [`fluent-plugin-concat`](https://github.com/fluent-plugins-nursery/fluent-plugin-concat).
14+
{% endhint %}
815

916
## Parameters
1017

0 commit comments

Comments
 (0)