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.

Sign up for GitHub

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

Jump to bottom

Clarified parser behavior in documentation #1392

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

Clarified parser behavior in documentation #1392

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
306f2ba
Clarified parser behavior in documentation
gvozdetsky Jun 14, 2024
1784fe8
wrap lines around 80 characters in length, and avoid words like i.e.
gvozdet Jul 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion pipeline/inputs/tail.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,11 @@ pipeline:
{% endtab %}
{% endtabs %}

The two options separated by a comma means multi-format: try `docker` and `cri` multiline formats.
The two options separated by a comma mean Fluent Bit will try each parser in the list in order, applying the first one that matches the log.

It will use the first parser which has a `start_state` that matches the log.

For example, it will first try `docker`, and if `docker` does not match, it will then try `cri`.

We are **still working** on extending support to do multiline for nested stack traces and such. Over the Fluent Bit v1.8.x release cycle we will be updating the documentation.

Expand Down