Intelligent Error Deduplication
When we receive an error from you, our first step is to see if it matches any you've sent us before. If it does, we group the errors together. Our UI lets you treat these groups of errors much like issues in an issue tracker. We also provide a rich set of tools for drilling down into the data from individual error occurrences for debugging.
Why do we deduplicate errors? If you've ever tried to fix a bug using your production logs, you know that errors are noisy. A single typo in your code can cause 100, 1,000, or more individual exceptions. RIP inbox.
Noisy error reporting slows you down and makes it nearly impossible to respond if several kinds of errors coincide. You may find the needle in the haystack - but how do you know there's only one needle?
Our deduplication techniques are a result of years of refinement. They work well for the vast majority of users. On the off chance that they don't work for you, we give you the option to define custom grouping programmatically. Implementation details vary by language, but for a typical example, see our Ruby custom error grouping docs.