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:
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:
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: You can use any attribute of incoming errors to make a rule - including custom data.
As well as this, Errordite has:
This is just the start and we have loads of ideas to make error management even better:
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!