New in Yeller: Event search, drilldown and advanced diagnosis

This is a blog about the development of Yeller, The Exception Tracker with Answers

Read more about Yeller here

Diagnosing errors can be tough. Often you have to dig deep into data about the error to figure out why it happened. These questions are usually pretty open in scope

  • What versions of Chrome did this happen on?
  • Did this error affect our client’s CEO?
  • Which companies were most affected by this error?

Most error tracking software out there doesn’t let you drill down to this level of detail. Instead they just throw up a list of events on a page, and let you open thousands of tabs and look at each one yourself.

If people are doing things over and over again, the computer should be doing it.

Machines are good at repetitive tasks

Yehuda Katz, ex Rails-Core member

That’s not good enough

Of course, what happens when you actually do need an answer to one of these questions manually? You start opening browser tabs, look through a few of the events, not all of them. You aren’t going to open 1000 browser tabs and summarize data across them

As of today, Yeller solves this problem entirely. No more guessing at context. Just answers. And it takes seconds to figure out what’s going on:

Which versions of Chrome did this happen on?

Did my client’s CEO get hit by this error?

Which companies were most affected by this error?

All of these searches work across any of the data you send to Yeller. HTTP params, Background Job arguments, the users who were affected, anything else you like.

Sign up today for error diagnosis superpowers

So, that’s it. Suddenly a whole load of questions you used to have about errors are easy to fix.

Sign up for your free 30 day trial today

Exceptions got you frustrated? Sign up to Yeller to automatically track them, and then fix them with your new diagnosis superpowers.

Yeller works with Clojure, Ruby, Rails, Java, JavaScript, Go, Haskell and Node.js