in_forward: add new option 'tag_prefix' (#4455) #4466
Merged
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 patch adds a new option called 'tag_prefix' that allows to prefix the
incoming Tag set by the remote client.
Usage:
--- config file ---
[SERVICE]
flush 1
log_level info
[INPUT]
name forward
tag_prefix new.
[OUTPUT]
name stdout
match *
--- end ---
$ echo "{"key": "test"}" | fluent-cat test
$ bin/fluent-bit -i forward -p tag_prefix=new. -o stdout -f 1
...
[0] new.test: [1639626354.501658295, {"key"=>"test"}]
Signed-off-by: Eduardo Silva [email protected]
Enter
[N/A]
in the box, if an item is not applicable to your change.Testing
Before we can approve your change; please submit the following in a comment:
Documentation
Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.