Timber.io is a cloud based logging platform, specifically engineered for Ruby, Elixir and Node apps. It automatically structures your log data with it's open source packages, makes the lines readable, adds valuable context, and lets you easily create graphs and alerts from your logs.
Coming from a heavy Loggly user, this is an amazing execution. Makes cloud logging super straight-forward along with powerful filtering options. I'll keep playing with it some more, but so far it looks very solid.Pros:
Beautiful interface, seamless installation, responsive support.Cons:
I just found it out
We've been using Timber in production for a while now at Exeq, and it's been mission critical to us. Having consolidated, searchable logging across our (5+) systems has been awesome. Love working with their team as well; they love feedback and take it very well. Their alerting is actually too verbose for our needs at times, but configurability is coming! Would highly recommend.Pros:
Design, usability, ease of implementation, speed of team.Cons:
Alerting, it exists but can be better...but having read future specs, there's a lot in the works that makes me excited!
If you use Rails+Heroku (or any of the other stacks they have special integrations for) I'd highly recommend it, as there are a bunch of convenient features you get out of the box, like being able to easily query the logs of a specific user, etcPros:
Brilliant, easy-to-use logging (and-then-some) in a beautiful, intuitive UI. Lots of useful, developer-friendly features that "just work."Cons:
That it's only coming out now!
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 instantCons:
- 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 servicesPros:
Beautiful interface, really expressive searchCons:
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.
Timber has been core to our infrastructure since day 1. It's drastically better and easier to use than the competition. I highly recommend you give it a try, you won't regret it!Pros:
Amazing product from a stellar team! It was the first SaaS product we started using with Intello and have benefited tremendously from it.Cons:
Slack alerts are a newish features, but really no complaints
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 supportCons:
A little light on 3rd party integrations
Before finding Timber.io I used to debug by other means and if that didn't work, I would ssh into the server logs because other log aggregation tools were too much overhead to setup. Needless to say I am very happy to have found TimberPros:
Ease of setup, great uiCons:
Want to be able to ignore sending certain logs (healthchecks, rollbar logs)