Timber
Log Better. Solve Problems Faster.
8 followers
Log Better. Solve Problems Faster.
8 followers
Timber is a new kind of cloud-based logging system designed for applications and developers. Spend less time debugging and more time shipping.
Launch Team
Framer AI AgentsDesign and publish professional sites with AI
Promoted
Switched over to timber months ago and it's been awesome to work in. Navigating to different times and filtering is really easy compared to Papertrail.
Pros:- Incredibly easy on-boarding
- Out of the box context for Elixir and Ruby apps
- Interface is very intuitive and searches are near instant
Cons:- Alerting can be improved by including loglines and more customization, but these are on the roadmap
This isn't really a con, but their ruby/elixir library allows you to attach user context data to logs and I would love to be able to easily do that in my Python + Go apps. Otherwise love the service - have used a bunch of different logging service in the past and this by far one of the easier to use services
Pros:Beautiful interface, really expressive search
Cons:Wish i could dismiss specific subsets of alerts
I've used Timber.io on CodeSponsor.io for a couple of months and have loved it. It is very easy to see real-time what is happening in the app and apply filters.
Pros:My favorite part was the installation process. So much thought was put into making this experience seamless. Huge kudos to the team!
Cons:No cons that I can see so far.
I've been using timber for a while now, on a bunch of elixir apps I've been writing in 2017. I must say it's the best experience I've had with any 3rd party logging system. I love the context functionality which can be used to group together log events in order to identify patterns quicker.
Whenever I've had a problem, David at Timber has always been there to help and is very responsive!
A handy tip: I use sentry.io for error reporting. The first thing I do when I see a sentry error pop up is:
- Copy the sentry error ID
- Paste it into timber's search bar for offending the application
- Find the sentry log message "Sending error <blah> to sentry.io" or something similar
- Click on the timestamp to see what happened around that log entry
A simple way to quickly get more context that sentry would never be able to provide.
Pros:Beautiful interface, easy to setup, amazing support
Cons:A little light on 3rd party integrations