Updated field names to match java counterparts supported by logstash crew #41
Conversation
This file contains 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
vklochan
added a commit
that referenced
this pull request
Nov 10, 2015
Updated field names to match java counterparts supported by logstash crew
Closed
|
This change is causing me to modify my config. Any tips on how to have the old field names mutate/morph into the new ones in logstash config? In the mean time I've pegged to 0.4.5 - this module does exactly what it needs to I'm not too worried about falling behind. Thank you @vklochan. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
#40
See detailed descriptions and naming convention at https://github.com/logstash/logstash-logback-encoder#standard-fields