Add documentation for systemd per-service parsing configuration #1508
+21
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Dennis Kaarsemaker <dennis@kaarsemaker.net>
seveas
force-pushed
the
systemd-parser
branch
from
cc4ea7b to
6928c51
Compare
eschabell
added
waiting-for-user
|
@esmerel can you give this a look? |
|
@seveas can you resolve the conflicts here? I also nudged you on the code PR fluent/fluent-bit#9567 for actions needed to proceed there. |
esmerel
approved these changes
Oct 22, 2025
| WantedBy=multi-user.target | ||
| ``` | ||
|
|
||
| `LogExtraFields` will make the specified fields appear in the log output. The `Systemd` plugin will look for a `FLUENT_BIT_PARSER` field and use it to parse the `MESSAGE` field. If the parser is not found or parsing fails, the unparsed message is added to the log entry as if no parser was specified. |
There was a problem hiding this comment.
Suggested change
| `LogExtraFields` will make the specified fields appear in the log output. The `Systemd` plugin will look for a `FLUENT_BIT_PARSER` field and use it to parse the `MESSAGE` field. If the parser is not found or parsing fails, the unparsed message is added to the log entry as if no parser was specified. | |
| `LogExtraFields` adds the specified fields to the log output. The `Systemd` plugin looks for a `FLUENT_BIT_PARSER` field and uses it to parse the `MESSAGE` field. If the parser is not found or parsing fails, the unparsed message is added to the log entry as if no parser was specified. |
| {% endtab %} | ||
| {% endtabs %} | ||
| ### Parsing the MESSAGE field |
There was a problem hiding this comment.
Suggested change
| ### Parsing the MESSAGE field | |
| ### Parsing the `MESSAGE` field |
|
It also looks like the conflict can be resolved safely by accepting the incoming changes, but github has a bad habit of marking suggestions as outdated when you merge things so I'm not doing it myself this time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This documents the functionality added in fluent/fluent-bit#9567