This is one of our biggest issues right now. Errors get groups by execution path, which for us is not the most accurate way to group them. Sometimes we get en exception in the same place but with a different content, which we need to be aware of. I am not an admin on my account so Im not sure exactly what options you have to customize this, but I have talked about this several times with my admin and they say there is not much we can currently do to solve this. I would like to know is there is any other option for this.
Hi there Hugo,
Thanks for reaching out! We do have options for further customizing error groups. You can set up your own custom error group hasher by creating a GroupingKey that sets your own grouping options, and passing the GroupingKey through on the error payload. By adding the GroupingKey in the onBeforeSend (https://github.com/MindscapeHQ/raygun4js#onbeforesend) method you can capture each payload and assign a custom error group id. There is a JavaScript example of setting up custom error grouping on our blog (https://raygun.com/blog/custom-error-grouping/).
All the best, and let me know if you have any further questions.
Get instant visibility into the health of your software to proactively identify and resolve issues before they impact your customers.
Raygun's suite of digital experience monitoring tools surfaces ac
With over 2.5 million reviews, we can provide the specific details that help you make an informed software buying decision for your business. Finding the right product is important, let us help.