Clarify parsing multiline messages (#10212)

make more clear the distinction between docker/cri splitting and merging, and multiline application log (stacktraces) merging

Signed-off-by: Martin Fleurke <[email protected]>

Author: Martin Fleurke

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

@@ -19,13 +19,13 @@ The Multiline parser engine exposes two ways to configure and use the feature:
 Fluent Bit exposes certain pre-configured parsers (built-in) to solve specific
 multiline parser cases. For example:
 
-| Parser   | Description                                                                                                                                                                                                                                                                                                                                        |
-|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `docker` | Process a log entry generated by a Docker container engine. This This parser supports the concatenation of large log entries split by Docker. If you use this parser, and you also want to concatenate loglines like stacktraces, you can add the [multiline filter](../../pipeline/filters/multiline-stacktrace.md) to specify additional parsers |
-| `cri`    | Process a log entry generated by CRI-O container engine. Like the `docker` parser, it supports concatenation of log entries                                                                                                                                                                                                                        |
-| `go`     | Process log entries generated by a Go based language application and perform concatenation if multiline messages are detected.                                                                                                                                                                                                                     |
-| `python` | Process log entries generated by a Python based language application and perform concatenation if multiline messages are detected.                                                                                                                                                                                                                 |
-| `java`   | Process log entries generated by a Google Cloud Java language application and perform concatenation if multiline messages are detected.                                                                                                                                                                                                            |
+| Parser | Description |
+| ------ | ----------- |
+| `docker` | Process a log entry generated by a Docker container engine. This parser supports the concatenation of large log entries split by Docker. If you use this parser, and you also want to concatenate loglines like stacktraces, you can add the [multiline filter](../../pipeline/filters/multiline-stacktrace.md) to specify additional parsers. |
+| `cri`    | Process a log entry generated by CRI-O container engine. Like the `docker` parser, it supports concatenation of log entries.            |
+| `go`     | Process log entries generated by a Go based language application and perform concatenation if multiline messages are detected.          |
+| `python` | Process log entries generated by a Python based language application and perform concatenation if multiline messages are detected.      |
+| `java`   | Process log entries generated by a Google Cloud Java language application and perform concatenation if multiline messages are detected. |
 
 ### Configurable multiline parsers
 

pipeline/filters/multiline-stacktrace.md

@@ -17,7 +17,7 @@ Along with multiline filters, you can enable one of the following built-in Fluen
 When using this filter:
 
 - The usage of this filter depends on a previous configuration of a [multiline parser](../../administration/configuring-fluent-bit/multiline-parsing.md) definition.
-- To concatenate messages read from a log file, it's highly recommended to use the multiline support in the [Tail plugin](https://docs.fluentbit.io/manual/pipeline/inputs/tail#multiline-support) itself. This is because performing concatenation while reading the log file is more performant. Concatenating messages that were originally one line, but split by Docker or CRI container engines because of their size, is supported in the [Tail plugin](https://docs.fluentbit.io/manual/pipeline/inputs/tail#multiline-support) icw the `docker` or `cri` parser. to concatenate application logs like stacktraces on top of that, you can use this multiline filter.
+- To concatenate messages read from a log file, it's highly recommended to use the multiline support in the [Tail plugin](https://docs.fluentbit.io/manual/pipeline/inputs/tail#multiline-support) itself. This is because performing concatenation while reading the log file is more performant. Concatenating messages that were originally one line, but split by Docker or CRI container engines because of their size, is supported in the [Tail plugin](https://docs.fluentbit.io/manual/pipeline/inputs/tail#multiline-support) in combination with the `docker` or `cri` parser. To concatenate application logs like stacktraces on top of that, you can use this multiline filter.
 
 {% hint style="warning" %}