Ask HN: How do you automate logging bugs in your product?

Recently at my place of work we've come into a bit of an issue with the way that log our bugs. Currently we automate logging many different types of exceptions and errors to our bug tracking system from our product. We're currently using unfuddle (which is a whole different religious war) to track bugs.

We've noticed that due to the automated manner of tracking bugs we have started to decrease our signal/noise ratio in our bug tracker due to the large number of duplicates that we're seeing. This makes triaging time consuming as we aren't sure which bugs are legitimate issues or possible duplicates of other bugs we've seen before.

Our team has been on a recent stent of patching noisy bugs as they come in, but it feels like these are merely bandaids to a larger problem.

How do you log bugs in your product in an automated manner without dirtying up your triaging process?

Some examples of bugs that we've been having issues with :

- Loops in automated processes can hit states that raise exceptions. These can generate a large number of bugs.

- Database restores that may fail in a staging/production environment