Feature Request
Allow polygamous merging of errors
Current Status:
Completed
Mathew Hartley
We get a few 'Resque::TermException' SIGTERMs which happen when Heroku shut down our background workers with autoscaling. The stack traces are never the same so these errors aren't ever grouped. I tried merging them, but only merging a pair of errors at a time is frustrating.
Please tell me that you'll be allowing more than two errors to partake in one merge in the future.
I support error harmony ??????.
Raygun
John-Daniel Trask
Posted on
Mar 11 2015
Hey Matthew,
Quick Q: Would this be the type of error in Ruby where you could detect it easily in code? I ask because we're looking at extending the the providers to provide your own grouping hash that would override our grouping logic (e.g. you could just set it to 'SHUTDOWN' or something, and it would all flow into its own group.
Our thinking is that it's probably easiest to do this at the provider level that trying to build an elaborate rules engine with nice UI in the app. We'd never be able to provide the flexibility that comes with just setting a bit in your code base.
Having said that, I'm keen to know if you can easily detect this type of error, perhaps you can't, at which point it might be best that we add a special rule for our ruby grouping hasher to detect this scenario and group it differently.
Cheers,
John-Daniel
Kev
Posted on
Mar 11 2015
That would be useful for JavaScript errors as well because of how the different browsers report the same error.
Raygun
John-Daniel Trask
Posted on
Mar 11 2015
Hi Kevin,
We have evolved our grouping code to frequently be able to group cross-browser errors together, even when the message differs and the stack looks subtly different too. It may be that you're using an older grouping algo at our end and we could upgrade you.
The reason we don't just automatically do this is because it generates new hashes for all new errors. This means old permanently ignored errors will then come back as new active errors which would confuse people. If it's not a biggy for you, and you're keen for us to upgrade you - ping me a note jdtrask@raygun.io. I'd appreciate your feedback on it too (it's also smart enough to know that IE localises messages and will group them, defaulting to English as the message).
Regarding the overall idea of setting a custom grouping value, we would look to bring that to all providers, Raygun4JS included.
Cheers folks,
John-Daniel
Mathew Hartley
Posted on
Mar 16 2015
It's not something that's easy to isolate in code. I have completely the opposite view for this 'elaborate rule engine' - it's never going to be 100% perfect, so making the dashboard more useful seems like an easy win (which is also a reason I'm using a SaaS error notification service over plain old emails).
Another case in point, Sendgrid is (currently) down and I now have 5 sequential 451 Authentication failed: Could not authenticate messages.
They're all from the same cause. In an ideal world you would select all 5 of them and hit merge. I appreciate that you can merge errors, I just don't understand why it's only possible for two at a time.
Mathew Hartley
Posted on
Mar 25 2015
Any updates? This is still very much a problem. UX/dashboard Video
Raygun
Zheng Li
Posted on
Jan 07 2021
Hi All,
Merging of multiple error groups (2+) was introduced a few years ago and customers can use it to merge error groups together quickly and easily.
What's more, in 2016 we introduced a custom grouping feature, that allows Raygun customers to group errors based on edge cases such as the error message.
If you'd like to learn more about how to get the best out of your error groups, then you might like to check out this article, which covers our four main strategies and tips.
Happy coding!
Zheng Li
VP of Product
Raygun