Timber Ruby Versions Save

? Great Ruby logging made easy.

v2.6.0-beta1

6 years ago

Fixed

  • Encoding and rewind issues for file upload parameters have been resolved. Timber improved attribute normalization across all contexts and events, ignoring binary values like this in general.

Changed

  • Attribute normalization has been strictly enforced across all event and context types.

v2.5.1

6 years ago

Fixed

  • Ensure the new content_length field for HTTP request and response events are an integer.

v2.5.0

6 years ago

Changed

  • Remove social promotions during the installation process
  • The default log device for development has been changed to a file (log/development.log) to follow Rails defaults.

Fixed

  • Adds an override for ActiveSupport::Buffered logger. This is a legacy class that was dropped in Rails >= 4. It lacked #formatter accessor methods, which was a bug that was never resolved.

Added

  • Capture content_length for both HTTP request and HTTP response events. This field is available in the log's metadata. The response event now includes the content length in the actual log message. The request message remains unchanged.

v2.4.0

6 years ago

Added

  • Adds the new host field into the http context, bumping the log event JSON schema to 3.2.0.

v2.3.4

6 years ago

Fixed

  • Fix bug calling Timber::Util::Request::REQUEST_ID_KEY_NAME12 to use the proper constant name.

v2.3.2

6 years ago

Fixed

  • Drop ASCII-8BIT (binary) data before encoding to JSON. This resolves encoding errors during this process.

v2.3.1

6 years ago

Fixed

  • Forcibly fallback to SSLv23 if SSLv3 fails. SSLv3 is only used for outdated OpenSSL versions.

v2.3.0

6 years ago

Added

  • Added the ability to pass additional loggers when instantiating a ::Timber::Logger.

v2.2.2

6 years ago

Fixed

  • Remove Railtie ordering clause based on devise omniauth initializer. This is no longer necessary since we do not integrate with Omniauth anymore.

v2.2.1

6 years ago

Changed

  • Omniauth integration was removed since it only captures user context during the Authentication phase. Omniauth does not persist sessions. As such, the integration is extremely low value and could cause unintended issues.