enable 'event_key' for non-raw setup. #39
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: Petur.Thorsteinsson <Petur.Thorsteinsson@tech-01.net>
Contributor
Author
|
It has been a while since this PR was made, but I still think it would be a useful feature. Any chance you could take a look at it @repeatedly ? :) |
|
Sorry we have not been able to respond. It may take some time, but we will. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
event_key is currently only supported when in 'raw' mode.
It will be beneficial to also have this option in the other mode - usually the event is a json object, and this enables the plugin to send just the log string as the event.
When compared to using just 'raw' mode - this method adds various benefits - such as being able to use 'use_fluentd_time'