This repository was archived by the owner on Dec 8, 2020. It is now read-only.
Releases: vectordotdev/timber-elixir
Releases · vectordotdev/timber-elixir
2.1.6 - 26 April 2017
- Updates the JSON schema URL to use the new 2.0 URL.
2.1.5 - 26 April 2017
- Allows
:hackney
1.8.0
as a dependency
2.1.4 - 26 April 2017
- Updates the JSON structure to follow the new 2.0 log event JSON schema. This is not a breaking change as the Timber API accepts both formats.
- Fixes an issue when truncating a binary and getting iodata. The resulting JSON would treat this as an array.
2.1.3 - 21 April 2017
- Normalizes array header values into comma delimited string as defined by the HTTP spec RFC 2616
- Adds a new configuration option
:header_keys_to_sanitize
allowing you to supply a list of string keys (case-insensitive) to be sanitized before being included in your logs. Note that the keys passed must be lowercase.
2.1.2 - 20 April 2017
- Improves the log messages of the
HTTPClientRequest
events. - Maps the
x-amzn-requestid
to therequest_id
attribute, if present and the traditionalx-request-id
is header is not present.
2.1.1 - 19 April 2017
- Automatically captures
hostname
for the system context.
2.1.0 - 19 April 2017
This release improves the reliabilty of the HTTP backend.
Breaking changes:
- Drops support for custom HTTP clients.
:hackney
is now included as a required dependency for the package.
Other changes:
- Removes the preflight check which was causing reliability issues (#137, #138)
- Fixes issue with logs being lost due to a greedy receive block (#138)
- Fixes issue with receive block entering potential infinite loop due to reference never suceeding (#138)
- Fixes issue where response messages about an asynchrnous request would not be handled correctly (#138)
Thanks to @johnhamelink for reporting the initial bug that led to the discovery of the issues above.
2.0.2 - 16 April 2017
-
Adds the appropriate runtime metadata keys to the
config :logger, :console, metadata: [...]
configuration option. Before, the config option looked something like:config :logger, :console, format: {Timber.Formatter, :format}, metadata: [:timber_context, :event, :application]
Now it should look like:
config :logger, :console, format: {Timber.Formatter, :format}, metadata: [:timber_context, :event, :application, :file, :function, :line, :module]
2.0.1 - 5 April 2017
- Small update to be more defensive with exception parsing. If parsing exceptions fails, they will be logged as traditional text log lines.
1.1.18 - 5 April 2017
- Small update to be more defensive with exception parsing. If parsing exceptions fails, they will be logged as traditional text log lines.