rg4js does not log errors with only one element in the stacktrace list
k.art
Posted on
Nov 30 2016
The first request does not show up in Raygun, the second one does. We've played around with it a bit and it seems if the stacktrace list has only one entry it does not go through.
Request URL: https://api.raygun.io/entries?apikey=y204tMf2EYB8M[..]G2kQ%3D%3D
Request Method: POST
Status Code: 202 Accepted
Body: {"OccurredOn":"2016-11-30T03:48:25.650Z","Details":{"Error":{"ClassName":"Error","Message":"raygun does not work","StackTrace":[{"LineNumber":32808,"ColumnNumber":24,"ClassName":"line 32808, column 24","FileName":"http://localhost:3000/static/bundle.js","MethodName":"at "}]},"Environment":{"UtcOffset":11,"Browser-Width":1279,"Browser-Height":676,"Screen-Width":1280,"Screen-Height":800,"Color-Depth":24,"Browser":"Mozilla","Browser-Name":"Netscape","Browser-Version":"5.0 (Macintosh; Intel Mac OS X 10116) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36","Platform":"MacIntel"},"Client":{"Name":"raygun-js","Version":"2.4.2"},"UserCustomData":{},"Tags":[],"Request":{"Url":"http://localhost:3000/","QueryString":{"session":"65034a0cefb4479382c02f600559da95"},"Headers":{"User-Agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10116) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36","Referer":"http://localhost:3000/?session=65034a0cefb4479382c02f600559da95","Host":"localhost"}},"Version":"Not supplied","User":{"Identifier":"c2ded316-3da1-dec4-215c-98aa8727a039","IsAnonymous":true,"UUID":"c2ded316-3da1-dec4-215c-98aa8727a039"}}}
Request URL: https://api.raygun.io/entries?apikey=y204tMf2EYB8M[..]G2kQ%3D%3D
Request Method: POST
Status Code: 202 Accepted
Body: {"OccurredOn":"2016-11-30T03:48:25.652Z","Details":{"Error":{"ClassName":"Error","Message":"Error while saving","StackTrace":[{"LineNumber":32665,"ColumnNumber":16,"ClassName":"line 32665, column 16","FileName":"http://localhost:3000/static/bundle.js","MethodName":"escalateError"},{"LineNumber":32812,"ColumnNumber":14,"ClassName":"line 32812, column 14","FileName":"http://localhost:3000/static/bundle.js","MethodName":"at "}]},"Environment":{"UtcOffset":11,"Browser-Width":1279,"Browser-Height":676,"Screen-Width":1280,"Screen-Height":800,"Color-Depth":24,"Browser":"Mozilla","Browser-Name":"Netscape","Browser-Version":"5.0 (Macintosh; Intel Mac OS X 10116) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36","Platform":"MacIntel"},"Client":{"Name":"raygun-js","Version":"2.4.2"},"UserCustomData":{},"Tags":[],"Request":{"Url":"http://localhost:3000/","QueryString":{"session":"65034a0cefb4479382c02f600559da95"},"Headers":{"User-Agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10116) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36","Referer":"http://localhost:3000/?session=65034a0cefb4479382c02f600559da95","Host":"localhost"}},"Version":"Not supplied","User":{"Identifier":"c2ded316-3da1-dec4-215c-98aa8727a039","IsAnonymous":true,"UUID":"c2ded316-3da1-dec4-215c-98aa8727a039"}}}
Alex
Posted on
Dec 01 2016
Hi there,
Stacktraces with a single line should be ingested and processed like any other. I tested with the payload posted and I found no issues viewing the issue.
What may have happened is that your above error got grouped into a permanently ignored error group (set to discard new instances).
If you fear you are losing legitimate error instances due to this behavior I would consider creating a custom grouping key which only takes affect for single line stacktraces. Docs
Hope that helps, let us know if you have any further questions.
Best regards,
Alex
k.art
Posted on
Dec 01 2016
Hi Alex,
Thanks for the quick reply. It looks that's exactly what happened. It's pretty confusing if completely different errors get merged together.
I will add the groupingKeyCallback.
Alex
Posted on
Dec 01 2016
I agree that different errors grouping unexpectedly can be confusing and it's something we try to avoid by releasing new versions of our grouping hashers to address known issues.
Unfortunately in cases where there is little meaningful stack trace data and a custom error message determining the best group can be relatively hard. I'll see if their's some improvements we can make to the next revision which help in this case.
Alex