Hot and fresh, v2 of the Timber ruby gem has just been released! v2 is the culmination of many hours of testing, talking to users, and learning. It packages a variety of enhancements, bug fixes, and performance improvements.
- Timber can now be installed with a simple command:
bundle exec timber install. (learn more)
- Timber now captures all HTTP request / response headers. This allows you to see a complete list of headers when inspecting requests and responses. (learn more)
paramsfor controller call events are now being captured. This allows you to inspect the parsed paramteres being sent to your controller. (learn more)
- Session IDs (
context.session.id) are now being captured as part of the context. (learn more)
- A number of the Timber integrations were previously using various Rails classes, these have been moved to simple Rack middlewares. This is a cleaner more generic approach.
- User context is now properly captured. In some cases this would not be included on the initial request log line, or captured at all.
- Test and development environments will remain untouched and display the plain text logs you’re accustomed to. In some cases Timber metadata was seen in these environments. This has been resolved.
- Checks for the existence of
logrageand resolves the conflict if that gem is installed.
- Capturing and logging all outgoing HTTP requests and responses. Helping you track and insepct outgoing HTTP activity. This is something we use internally at Timber that has been immensely helpful, as it simplifies monitoring and debugging communication with external APIs.
- Anything you’d like to see? Let us know! Just start a chat below. We love feedback and feature requests.
~> 2.0in your
# Gemfile gem 'timber', '~> 2.0'
bundle update timber.
bundle exec timber install your-api-key.
Remove any code you had in place to capture user contexts. As noted above, this issue has been fixed.
config.logger =call in your
config/environments/production.rb. This is now handled in