🌲 Great Elixir logging made easy
Fixed an error where Timber.Integrations.PhoenixInstrumenter
would cause an error during blacklist checks if the blacklist had not been set up.
Fixed an error where Timber.Integrations.PhoenixInstrumenter
would fail on render events for conn
structs that did not have a controller or action set. For example, when a conn
did not match listed routes, a 404.html
template would be rendered that did not have a controller or action. The render event would still be triggered though.
Timber.Integrations.PhoenixInstrumentater
. This will suppress log lines from being written for any controller/action pair.query_time
could be nil
in the EctoLogger
.~> 1.9
Timber.Eventable
protocol. #210
Timber.Events.ChannelJoinEvent
and Timber.Events.ChannelReceiveEvent
respectively. [#194]
Please disable the default channel logging as Timber will capture these events for you:
# web.ex
def channel do
quote do
- use Phoenix.Channel
+ use Phoenix.Channel, log_join: false, log_handle_in: false
hackney
to 1.8.6
since other versions are not stable. There are compatibility issues with idna underlying OTP versions.:dev
from the default list of environments to include when installing.:info
level specification to use the default Ecto
log level.Timber.Utils.Map.recursively_drop_blanks/1
Timber.Contexts.JobContext
struct with the new attempt
and queue_name
fields.capture_bodies
option to the Timber.Integrations.ExAwsHTTPClient
module that enables / disables the capturing of HTTP request and response bodies within the logs.ExAws
integration to structure and log outgoing ExAws
requests. You can configure this to only log destructive events or specific services.