Add access to the EMF data as map[string]interface{} #11
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.
Provide ability to retrieve the raw EMF data
In order to include the
"_aws"
as a named attribute in our logging system we would like to create it with your library (excellent and clean), but then apply it with our normal setup.Example with our current solution and embedding some statistics in our logs as named value pairs:
To add EMF with this lib we would like to add a function for EMF that is plug and play with current logging interface, like:
With current implementation we would need to unmarshal the bytes from log:
I see this mainly as a convenience method, but we would really love to see it, or something similar, included.