What you can do
- Trace HTTP requests
- Inspect HTTP requests & their parameters
- Tail a user
- Inspect Rack logs and view their associated metadata
- Search on Rack structured data
- Alert on Rack structured data
- Graph & visualize Rack structured data
⚠ If you are using Rails, this integration is installed automatically. There is nothing you need to do.
config.rufile, insert the Timber middleware:
1 2 3 4
# config.ru Timber::Integrations::Rack.middlewares.each do |middleware| use middleware end
Timber allows you to disable this integration entirely, reverting all
Rack logs to their previous unstructured, pre-Timber format. Please note, it is highly recommended to avoid doing this as it provides the means to perform very useful actions, such as tracing HTTP requests. If you are attempting to reduce log data, please see the optimizing data usage doc.
To disable this integration, simply set the following configuration flag:
# config/initializers/timber.rb Timber.config.integrations.rack.disable = true
For finer grained control, you can disable each specific Rack integration like so:
1 2 3 4 5 6
# config/initializers/timber.rb Timber.config.integrations.rack.error_event.disable = true Timber.config.integrations.rack.http_context.disable = true Timber.config.integrations.rack.http_events.disable = true Timber.config.integrations.rack.session_context.disable = true Timber.config.integrations.rack.user_context.disable = true
Each is described below:
error_eventdisables the structuring of exceptions. By disablign this integration exceptions will appear as multi-line raw text logs.
http_contextdisables setting the
httpcontext. It is highly recommended to avoid this, as it provides the mens to perform very useful features, like tracing HTTP requests.
http_eventdisables the structuring of
session_contextdisables setting the
user_contextdisables setting the