Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

administration:configuring-fluent-bit:multiline-parsing flush_timeout… #1234

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

MrPibody7
Copy link
Contributor

Multiline Parser flush_timeout does not have a default value. gh-595

… no default

Signed-off-by: Enrique Sibaja Pastrana <enrique@calyptia.com>
Signed-off-by: Enrique Sibaja Pastrana <enrique@calyptia.com>
@@ -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 | <p>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. </p><p></p><p>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 <code>key_content</code> configuration property (see below).</p> | |
| 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. The minimum value is 500 milliseconds. | |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the default?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ping @MrPibody7

@lecaros lecaros removed their request for review February 22, 2024 14:45
Copy link

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.

@github-actions github-actions bot added the Stale label May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants