Unexpected grouping of errors

Hi there,

I have been receiving email notifications when exceptions have been captured in our web service with a particular "message" in the email. This "message" is shown in the "Error Reports" table in the dashboard view.

I have basically been assuming that this is the actual exception message that was thrown by our code. However when I look at some of the error details in the raygun web UI the exceptions under the same "group" (i.e. with the same message title) have different message property values in the "Raw data".

Is this expected behaviour? I find it very confusing and misleading (or I'm just not understanding it properly!).

I can provide you with specific examples from my Raygun account if needed.

Cheers,

Isaac

---

Hi Isaac,

This behavior is part of Raygun's backend logic - we perform grouping based on the code path of the exception in order to group as close to the actual bug as possible. This is done on a per-language basis as the quality of that data varies amongst the languages. In general we have found that including the message relates in a poor grouping experience as this often contains instance-specific data, for example query strings in a web exception scenario that lead to instances being split out when they should be combined.

We can take a look at the instances that you're seeing combined when you expect them to be split out, and let you know why this is so, and look at any additions we might need if we need to cater for a new case. You can email me at callum at mindscape dot co dot nz if you'd like me to investigate your grouping, providing links to two error instances preferrably.

Regards,

Callum Gavin
Mindscape Limited

---

I have this problem as well, we're using the Ruby provider. Here's an example of the issue .

---

Hi Mathew,

By the looks of things these errors have different stack traces (if subtly).

We recommend is manually grouping these errors together in this instance.

Regards, Alex

---

Hi Alex (and Isaac, sorry for hijacking),

The differences are because our templating language creates dynamic html files as part of the rendering process, so they're always going to be subtly different stack traces.

If (in future) raygun would be able to have enough lenience to group these errors (essentially any error that's caused through our view layer) I would appreciate it.

Thanks,

Mathew

---