Home/ Questions/Q 71983
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T19:58:24+00:00

I’ve developed a Proof of Concept application that logs unhandled exceptions from an application

  • 0

I’ve developed a ‘Proof of Concept’ application that logs unhandled exceptions from an application to a bug-tracking system (in this case Team Foundation Server, but it could be ANY bug tracking system). A limitation of this idea is that I don’t want duplicate Bug Items opened every time the same exception is thrown (for example, many users encounter the exception – it’s still a single ‘bug’).

My first attempt was to store the Exception Type, Message and Stack Trace as fields in the Bug Tracking System.The logging component would then do a query against the Bug ‘Store’ to see if there is an open bug with the same information. (This example is .NET – but I would think the concept is platform independant).

The problem obviously is that these fields can be very large (particularly the stack trace) – and requires a ‘Full-Text’ type of implementation to store them and the searching is very expensive.

I was wondering what approaches have been defined for this problem. I had heard that FogBugz for example had such a feature for automated bug tracking, and was curious how it was implemented.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. You could create a checksum hash of the stack trace and store that as an indexed column. That way the query to the Bug Store would be pretty fast to avoid duplicates on insert.

    • 0