This repository was archived by the owner on Dec 8, 2020. It is now read-only.
Releases: vectordotdev/timber-elixir
Releases · vectordotdev/timber-elixir
0.4.6 - 29 November 2016
- Removes the
Any
implementation forTimber.Eventable
and documents how to set this up in your app instead. - Merges custom contexts into a maintained context map instead of requiring the user to manage that theirselves.
- Namespaces custom events with their
type
key before sending to the Timber API.
0.4.3 - 23 November 2016
- Removes experimental
Timber.Events.OutgoingHTTPRequestEvent
.
0.4.2 - 23 November 2016
- Adds new
Timber.Eventable
protocol for converting data structures into aTimber.Event.t
. This allows you to pass anything that adheres to this protocol in the:timber_event
metadata key. - Updates
Timber.Event
to define a behavior allTimer.Event.t
modules must follow. - Adds
Timber.Event.message/1
for extracting a loggable message from aTimber.Eventable.t
. - Adds
Timber.Event.logger_tuple/1
for conveniently generating aLogger
message and metadata. - Updates
Timber.Eventable
docs with examples.
0.4.0 - 16 November 2016
- Allows custom events to be used
- Allows use of logfmt in development
- Updates HTTP context to include certain request specific details
- Add Error Handler
- Escapes new lines on Heroku
0.3.2 - 11 November 2016
- Changes
HTTPRequestContext
toHTTPContext
- Appropriately passes up
http
instead ofhttp_request
for the context field - Allows Poison 3 to be used
- Fixes how the remote address of the client was being determined
0.3.1 - 11 November 2016
- Fix naming issue for event transformation
0.3.0 - 11 November 2016
- Adds Phoenix Instrumentation
0.2.3 - 10 November 2016
- Adds the ability to not print the log level in messages
- Sets the log level and timestamp to not print by default
v0.2.2 - 09 November 2016
- Use Map.drop/2 properly
0.2.1 - 09 November 2016
- Fixes an issue where the request ID for a context is set incorrectly