Examples:
1. your exception messages contain the id of the entity you're dealing with "FooBar 1234 has broken". You only want to match then on the FooBar has broken bit, not the 1234.
2. for whatever reason, some IP address keeps sending you dodgy requests that break your server. You can filter all errors requests from this IP address so you don't get swamped with these errors.
3. The same bug deep down in your code is causing different errors higher up. You can choose to match on the part of your stack trace that is the common cause and get all these errors attached to the same issue.
I guess #3 is the only example that might apply to me, but I have literally never had this happen, so I don't know. Then again, I don't even use Sentry, I get the issues emailed to me and I fix them on the spot (they're usually 1-line fixes, typos, or something like that).
We developed Errordite as a result of working on large(ish) eCommerce websites where the wide variety of errors produced made it impossible to understand exactly the different things that could be going wrong - and I think for this kind of thing, where you are not going to always be on top of your errors, Errordite is invaluable.