timber changelog

Changelog History

• v3.1.2 Changes

  April 05, 2019

  🔄 Changed

  • The Timber.Formatter no longer prints in a proprietary format with the @metadata delimiter. It not just print simple JSON lines. As such, the Timber.Formatter is not recommended for use in development or test environment unless you want JSON formatted logs.

• v3.1.1 Changes

  March 16, 2019

  🔄 Changed

  • Added support for the new Timber API keys. The :source_id parameter is now supported when configuring :timber in addition to the :api_key. This does not break backwards compatibility.

• v3.1.0 Changes

  February 25, 2019

  🔄 Changed

  • Timber.InvalidAPIKeyError is now Timber.Errors.InvalidAPIKeyError
  • Events are no longer nested under the event key.
  • Custom events are no longer nested under the event.custom key, they have simply been moved to the root of the document.
  • Custom contexts are no longer nested under the context.custom key, they have simply been moved to the root of the document.
  • JSON representations of log events no longer include the $schema key since Timber 2.0 does not strictly require a schema anymore.
  • All Timber.Events.* and Timber.Contexts.* structs have been deprecated in favor of simple maps since Timber 2.0 no longer requires a strict schema. Module docs for each module has been updated accordingly.
  • Errors are no longer automatically parsed in the logger backend. Please use the :timber_exceptions library if you'd like to structure errors. This is a proper approach to structuring these events.
  • Handle unencodable content

• v3.0.0 Changes

  December 20, 2018

  ⬆️ 3.0.0 contains breaking changes, for upgrade instructions see [UPGRADING.md](./UPGRADING.md)

  🔄 Changed

  • Jason is now used for JSON encoding. The JSON library can no longer be injected via configuration.
  • msgpax 1.x is no longer supported
  • Logs are now sent in batches of 1000 instead of 5000 to comply with the Timber library specification
  • Timber.LoggerBackends.HTTP.TimberAPIKeyInvalid is now Timber.InvalidAPIKeyError

  ✂ Removed

  • Removed support for Elixir 1.3 and lower
  • Removed integration with Phoenix; use the :timber_phoenix package instead
  • Removed integration with Plug; use the :timber_plug package instead
  • Removed integration with Ecto; use the :timber_ecto package instead
  • Removed integration with ExAws
  • Removed integration with :error_logger; use the :timber_exceptions package instead
  • Removed the installer (mix timber.install); manual installation is now expected
  • Removed the test event Mix task

  🚀 [Unreleased]: https://github.com/timberio/timber-elixir/compare/v3.1.2...HEAD

• v3.0.0-alpha.3

  October 08, 2018

• v3.0.0-alpha.2

  October 01, 2018

• v3.0.0-alpha.1

  September 28, 2018

• v2.8.4 Changes

  August 14, 2018

  🛠 Fixed

  • The hostname caching released in v2.8.3 had the potential to crash the Logger if an application was started between :logger and :timber and made Logger calls. This was because the ETS table holding the cache had not been started by Timber yet. To fix this, the hostname is now cached in the application environment which is guaranteed to be available by that point.

• v2.8.3 Changes

  August 13, 2018

  🔄 Changed

  • The system hostname is now cached after it is fetched the first time.
    🌲 Previously, the hostname was fetched every time a log line was formatted for
    output (whether by formatting occured in the console formatter or during
    HTTP transport). This reduces the overhead caused by fetching the hostname.

• v2.8.2 Changes

  August 13, 2018

  🔄 Changed

  • 👍 Allow ~> 2.0 for the :msgpax dependency.