[breaking change] remove log_format #53
Closed
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.
As part of our new kubernetes solution, we are pursuing more declarative config all around. Some configuration that we currently support like
log_format
oradd_timestamp
could instead be done in a filter plugin like therecord_modifier
plugin.However, in order to support both
text
type formats andjson
type formats, while also preserving_sumo_metadata
, we need to change the expected format of the input. Now the log message to be sent to sumo is wrapped in the"message"
key, as shown in the unit testsThis is a breaking change and will require a major release
2.0.0