New in Yeller: Ocurrence Graphs

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

Read more about Yeller here

So exactly when has this exception ocurred in production?

Knowing when an exception happened is a powerful tool. It lets you correlate with deploys, with recurring scheduled tasks in your infrastructure, with daily emails, and more.

As of today, Yeller comes with graphs of exception occurrences built in:

Yeller stores these at high resolution for recent data, and rolls up older data.

Graphs start from right now, even if there’s no exception data in that time period. This means you can answer “is this exception still happening” as soon as you look at the page.

A thing I’m particularly excited with timeseries graphs is the opportunity to correlate with your own infrastructure metrics. Some exceptions only happen under particularly high throughput rates, or when particular latencies rise, etc. With timeseries graphs of occurrences, Yeller helps you correlate that data.

So, go check it out. Yeller now has timeseries data, complementing the smart debugging tools it already has. This is another step in helping you to really understand your exceptions, so you can fix them faster.

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

Read more about Yeller here

Looking for more about running production applications, debugging, Clojure development and distributed systems? Subscribe to our newsletter: