Question

I've installed the fogbugz django middleware to report 404s and 500s to Scout Submit, and am liking the functionality, but all the 500 errors at a given URL are using the same fogbugz case title, such as:

Error (EXTERNAL IP): /

The effect is that a new problem can re-open the case for an old problem and put NEW and VERY DIFFERENT traceback info at the bottom of the page.

Before I start hacking the middleware to include a more descriptive title, such as:

Error: / TemplateSyntaxError: Invalid filter: 'bad_filter'

am I doing something wrong, or does anyone else have a solution?

Answer 1

You're not doing anything wrong; in the use case that I originally wrote FogBugz Middleware for—an extremely RESTful web service—I didn't get 500s enough to bother distinguishing on exception type. Although you're entirely welcome to hack it yourself, if you instead file a bug, I'll be happy to do it for you in the very near future.

Just as a reminder, although I do work at Fog Creek Software, FogBugz Middleware is not currently a Fog Creek product.