Ignoring

Hi,

We've just moved from an older version of our grouping code to a newer version on all new apps. The previous version would have grouped them separately but the new one won't. This is an oversight and we're going to put explicit handling in to split them out so each unique URL would be a different error group (so you could permanently ignore the ones coming from vulnerability scanners etc, but still see the ones that you could fix).

I'll update this thread once this change is rolled out.

Thank you for drawing my attention to this,

John-Daniel Trask
Co-founder
Mindscape Limited

Hi Benny,

We're going to look into this on Monday. I've been discussing it with the developer of our Rails provider. We'll flip you over once it's ready.

I'm thinking we'll look at taking into account the first line of the stack trace:

Method name Class name

We won't use line since it could move on every release but still represent the same issue.

I'll update the thread once something is live for you. Sorry about the delay.

John-Daniel Trask
Co-founder
Mindscape Limited

Hi Benny,

We've updated the error hashing for the Ruby provider, and as such you should now be seeing improved grouping for errors with the same name, e.g. "undefined method `name' for nil:NilClass", but different causes. It will now only group errors together if they have the same method name and file name as John-Daniel detailed above.

Hope this helps improve your Raygun experience.

Regards,

Callum