Erlang interop - logger level and timestamp change #16
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.
Use Erlang logger level
Elixir 1.11 introduces
erl_levelin metadata to put the correct level, while passing old level for backward compatibility.Use the "correct" logger level, if found (e.g. in Elixir 1.11)
This will change the
levelfrom output jsonUse Erlang time
Erlang actually put
timemetadata - which is unix timestamp with microsecond - so we can get DateTime - while Elixir Logger passes {date, time} tuples which does not have timezone.Let's use the timestamp from erlang - under the same key (
timestamp) for now.This will change the format of timestamp - adding
Z