Skip to content
This repository was archived by the owner on Dec 8, 2020. It is now read-only.

Releases: vectordotdev/timber-elixir

2.1.6 - 26 April 2017

26 Apr 06:20
Compare
Choose a tag to compare
  • Updates the JSON schema URL to use the new 2.0 URL.

2.1.5 - 26 April 2017

26 Apr 05:55
Compare
Choose a tag to compare
  • Allows :hackney 1.8.0 as a dependency

2.1.4 - 26 April 2017

26 Apr 05:46
Compare
Choose a tag to compare
  • 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

21 Apr 23:35
Compare
Choose a tag to compare
  • 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

20 Apr 16:18
Compare
Choose a tag to compare
  • Improves the log messages of the HTTPClientRequest events.
  • Maps the x-amzn-requestid to the request_id attribute, if present and the traditional x-request-id is header is not present.

2.1.1 - 19 April 2017

19 Apr 18:23
Compare
Choose a tag to compare
  • Automatically captures hostname for the system context.

2.1.0 - 19 April 2017

19 Apr 16:32
Compare
Choose a tag to compare

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

17 Apr 02:01
Compare
Choose a tag to compare
  • 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

06 Apr 04:30
Compare
Choose a tag to compare
  • 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

06 Apr 04:31
Compare
Choose a tag to compare
  • Small update to be more defensive with exception parsing. If parsing exceptions fails, they will be logged as traditional text log lines.