How errors are grouped/distinguished

How are errors groups/distinguished? Is it just based on the error message? What is two errors are reported with the same message, eg: "Data failed to load" but they had different stack traces. Would that be two error types or one?

Thanks John - that sounds sufficient then.

Hi John,

Do you recommend then that we keep contextual information out of error messages, so that in the case where the stack trace or some other signal cannot be used, then RayGun would still be able to successfully group by message?

Does RayGun used the exception type name to perform grouping? Ideally we could use specific exception names that have contextual messages and these would be grouped as the same error without having to lose helpful message details.

Thanks,

Joel

Yes we've been debating the same thing. If the error message is "Login error for user 123" that gets filed as a distinct error from "Login error for user 345". Would be nice to be able to provide some kind of optional error grouping key ("login_error_for_user"). I'd think this would be different from grouping based on the exception type, eg: NullReferenceException that could occur in many places that are really distinct errors.

"The ability to send your own grouping key is in development at present."

Is this still true? I'm looking for such an option but can't find anything about custom/forced group keys in the javascript documentation.

I'd need this for the following scenario:

I'm receiving responses for many different requests from the server in an asynchronous manner. Since all those responses are basically handled (and passed on accordingly) in one place, they all have the same stack trace, when an error is recognized and handled there.

I already create meaningful (but still generic) error names from information within the erroneous response which I'd like to use for grouping inside raygun. Since raygun automatically groups by stack trace and ignores the error name many unrelated errors are collected in one big group which is pretty inconvenient for us.

I'd really appreciate if you could add an option to either ignore the stack trace for grouping or to force the group name. Since in general grouping by stack trace is very welcome, I'd like to set this option per sent error instance and not at initialization time.

Please let me know if I can expect something like this to come soon. Otherwise I'd have to look for some different solution/hack (remove or modify stack trace manually before sending if possible, ...).

Thanks & best regards

We too would be very excited to take advantage of a "grouping key". It would give us some better control over alerts, possibly also satisfying a suggestion I made quite a while back to allow for some sort of custom alerting: https://raygun.io/thinktank/suggestion/10405

Is there a rough eta on its availability (weeks, months, etc..)?

Steve

I'd really appreciate an response here.

Right now the automatic grouping by stack trace is making the error handling on raygun really cumbersome to us since most of our javascript errors are reported in the same group even though they have distinct error messages.

This makes the daily e-mail-reports & slack integration pretty much useless since we have to check every single reported error manually in the "backend" to know what it really was about.

Please give us at least an answer to the question of whether there is an option in development/planed or not.

Thanks

Hi,

We've got a big release planned for next week, so once that has calmed down I'll get the team to start working on this. It's going to take a while to add support for setting your own custom grouping key in all the client libraries we have, but we'll roll these out slowly as they're updated. All going to plan, we'll have this out before the end of the year.

Cheers,
Jamie