Skip to content

Commit 783945a

Browse files
Apply suggestions from code review
Co-authored-by: Adam Locke <[email protected]> Signed-off-by: Lynette Miles <[email protected]>
1 parent 45de608 commit 783945a

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

administration/configuring-fluent-bit/multiline-parsing.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,8 @@
22

33
In an ideal world, applications might log their messages within a single line, but in
44
reality applications generate multiple log messages that sometimes belong to the same
5-
context. Processing this information can be complex, like in application stack traces which always have multiple log lines.
5+
context. Processing this information can be complex, like in application stack traces,
6+
which always have multiple log lines.
67

78
<img referrerpolicy="no-referrer-when-downgrade" src="https://static.scarf.sh/a.png?x-pxid=e19a4c14-a9e4-4163-8f3a-52196eb9a585" />
89

@@ -33,7 +34,9 @@ multiline parser cases. For example:
3334
You can define your own Multiline parsers with their own rules, using a configuration
3435
file.
3536

36-
A multiline parser is defined in a `parsers configuration file` by using a `[MULTILINE_PARSER]` section definition. The multiline parser must have a unique name and a type plus other configured properties associated with each type.
37+
A multiline parser is defined in a `parsers configuration file` by using a
38+
`[MULTILINE_PARSER]` section definition. The multiline parser must have a unique name
39+
and a type, plus other configured properties associated with each type.
3740

3841
To understand which multiline parser type is required for your use case you have to
3942
know the conditions in the content that determine the beginning of a multiline

0 commit comments

Comments
 (0)