Anyone logging to
STDOUTwill be pleased to know that v2 now uses the
Loggerbackend included with Elixir. Functionally this performs exactly the same, but the benefits of using a standard library include: improved stability, better performance, active ongoing maintenance, etc.
The installer has been vastly improved:
- It now recognizes umbrella applications, handling them accordingly.
- A bug was squashed for Phoenix versions 1.3, the installer should work great there as well.
- The whole flow has been refined to use better messaging, formatting, and pauses that make it more apparent when user action is needed.
Re-run the single command installer (
mix timber.install). This commend, with your API-key, is located in the settings of your application.
NewTimber Elixir V2 ReleasedMay 23rd, 2017
V2 of our Elixir library is now available. V2 includes a variety of improvements, notable changes are listed below.
We've placed an
file in our repo. The process is very simple:
Eenjoy! Happy logging.
ImprovementShorter, Easier Field PathsMay 23rd, 2017
We're always looking for small subtle changes that could improve the UX of Timber. Today we released what we're calling "short paths." Here's a simple example:
Instead of issuing a query like:
You can now do:
Here are a few more examples:
|Long field path||Short field path|
Give it a try!
NewView a Line in ContextMay 23rd, 2017
Have you ever searched for a line and wanted to view it in the context of it’s HTTP request? Today we added a tag that makes this as easy as a click.
View logs in context is often critical to resolve issues quickly. And we’re constantly looking for ways to make this easier.
We also added a new docs page for this feature.