• Docs  › 
  • About

About Errordite

We have spent years helping develop busy websites and seeing the large numbers of errors that fill up the logs. Some of these errors were caused by genuine bugs that slipped into production, while many others were the result of unexpected URLs from a searchbot or once-a-day database contention problems, caused by some heavy-duty SQL job running at 3am. The variety of severity and frequency of these different types of errors combined with the flat, distributed and un-parseable nature of the error logs meant dealing with these errors in any proactive way was near-impossible.

Errordite was developed as a solution to these problems, with 2 main goals in mind:

  1. to show you exactly what issues are being experienced by an application (that is to say the underlying problems resulting in errors)
  2. to help you to process these issues - assign them to someone to be investigated and fixed them or else choose to ignore them

On the face of it, the natural way to categorise errors into issues is by their exception type and the method from which they were thrown, and indeed this is Errordite's default mode. But sometimes this doesn't work. For example:

  1. multiple different errors result in the same exception type (because of overzealous exception wrapping or because the precise error is explained in the exception message)
  2. conversely, a bunch of different exceptions all come from the same root cause, and you want to consider them the same issue

To get around these scenarios, Errordite has an intuitive and powerful visual rule creation facility to allow you to redefine an issue so that it includes a more (or less) precise set of errors. Check out the video on the home page to see how it works - but in a snippet it looks like this: Rule matching example You can use any attribute of incoming errors to make a rule - including custom data.

Features

As well as this, Errordite has:

  • a live updating dashboard, so you can see errors happening in real time
  • alerts when a new issue occurs, or a solved issue recurs
  • graphs to show you the historical number of occurrences of an issue per day plus their distribution over 24 hours
  • quick Lucene-based search
  • the ability to receive custom data with each error
  • an overall activity log so you can see exactly who has done what to which issues
  • integration with HipChat / CampFire

Roadmap

This is just the start and we have loads of ideas to make error management even better:

  • alerts when your error activity changes unexpectedly
  • logging of application trace information
  • integration with bug tracking software
  • integration with more chat services
  • more visualisations

Errordite will not only help you manage and fix your errors but it may well tell you about errors your users see but that you didn't even know existed. Sign up and start managing your errors!