From 6e08207d66e8a8497d24757e79a6afad86371780 Mon Sep 17 00:00:00 2001 From: Enrique Sibaja Pastrana Date: Fri, 13 Oct 2023 16:55:05 -0600 Subject: [PATCH 1/2] administration:configuring-fluent-bit:multiline-parsing flush_timeout no default Signed-off-by: Enrique Sibaja Pastrana --- administration/configuring-fluent-bit/multiline-parsing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/administration/configuring-fluent-bit/multiline-parsing.md b/administration/configuring-fluent-bit/multiline-parsing.md index f6fa1e379..fbb5270bf 100644 --- a/administration/configuring-fluent-bit/multiline-parsing.md +++ b/administration/configuring-fluent-bit/multiline-parsing.md @@ -37,7 +37,7 @@ To understand which Multiline parser type is required for your use case you have | type | Set the multiline mode, for now, we support the type `regex`. | | | parser |

Name of a pre-defined parser that must be applied to the incoming content before applying the regex rule. If no parser is defined, it's assumed that's a raw text and not a structured message.

Note: when a parser is applied to a raw text, then the regex is applied against a specific key of the structured message by using the key_content configuration property (see below).

| | | key_content | For an incoming structured message, specify the key that contains the data that should be processed by the regular expression and possibly concatenated. | | -| flush_timeout | Timeout in milliseconds to flush a non-terminated multiline buffer. Default is set to 5 seconds. | 5s | +| flush_timeout | Timeout in milliseconds to flush a non-terminated multiline buffer. | | | rule | Configure a rule to match a multiline pattern. The rule has a specific format described below. Multiple rules can be defined. | | #### Lines and States From 1022a030d0931ddeb6daadff84155bf24e92c956 Mon Sep 17 00:00:00 2001 From: Enrique Sibaja Pastrana Date: Mon, 16 Oct 2023 11:21:31 -0600 Subject: [PATCH 2/2] GH-595: Adding-The minimum value for flush_timeout is 500 ms Signed-off-by: Enrique Sibaja Pastrana --- administration/configuring-fluent-bit/multiline-parsing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/administration/configuring-fluent-bit/multiline-parsing.md b/administration/configuring-fluent-bit/multiline-parsing.md index fbb5270bf..d1352e3ca 100644 --- a/administration/configuring-fluent-bit/multiline-parsing.md +++ b/administration/configuring-fluent-bit/multiline-parsing.md @@ -37,7 +37,7 @@ To understand which Multiline parser type is required for your use case you have | type | Set the multiline mode, for now, we support the type `regex`. | | | parser |

Name of a pre-defined parser that must be applied to the incoming content before applying the regex rule. If no parser is defined, it's assumed that's a raw text and not a structured message.

Note: when a parser is applied to a raw text, then the regex is applied against a specific key of the structured message by using the key_content configuration property (see below).

| | | key_content | For an incoming structured message, specify the key that contains the data that should be processed by the regular expression and possibly concatenated. | | -| flush_timeout | Timeout in milliseconds to flush a non-terminated multiline buffer. | | +| flush_timeout | Timeout in milliseconds to flush a non-terminated multiline buffer. The minimum value is 500 milliseconds. | | | rule | Configure a rule to match a multiline pattern. The rule has a specific format described below. Multiple rules can be defined. | | #### Lines and States