Crash reporting, loads of neat features that help heaps Review collected by and hosted on G2.com.

Cost of real-time user monitoring, just not really affordable (for me at least) Review collected by and hosted on G2.com.

Our bug priorities depend on number of affected users Review collected by and hosted on G2.com.

node.js grouping for errors may be more customization would be good for example, sometimes I'm getting errors from third party so I can turn on grouping by error message, the problem is that sometimes I need to distinguish errors by message and stack trace. like database errors or errors from http requests Review collected by and hosted on G2.com.

Real-time reporting is critical, especially right after a release, where potentially the first few errors reported could have a severe impact. Review collected by and hosted on G2.com.

Sometimes it's challenging to figure out where the error is coming from in a minified script (e.g., "error at ? line 1, column 2669688"). Review collected by and hosted on G2.com.

The website is very easy to use. I am able to locate errors very efficiently. Review collected by and hosted on G2.com.

The down time that happens every so often. Specifically, if AWS goes down then Raygun goes down. It would be nice if they had a backup plan to never be down. Review collected by and hosted on G2.com.

The ability to search errors by userId to see if we captured a logged error for a given customer contacting us. Review collected by and hosted on G2.com.

It is easy to get into a situation where you are logging too much, and the reports may become noise. Review collected by and hosted on G2.com.

I've found the Slack integration to be invaluable as the team has visibility on issues as they happen Review collected by and hosted on G2.com.

Sometimes the alerts/notifications are too verbose for non-tech (CS/Support) users to parse without dev assistance Review collected by and hosted on G2.com.

It's easy to do an initial setup, with additional features available with some additional configuration. Raygun makes it easy to analyze performance, and to understand how users use my software - like a Google Analytics light combined with error reporting.

I mostly use the Crash Reporting and the User-tracking features. It's incredibly useful to be notified about an error and then have the option to contact all affected users before they contact me. Makes it very professional. I can also see everything in the user's session - and is therefore able to recreate the error fully in development. Review collected by and hosted on G2.com.

I do think that it would be nice to have more options available for notifications. But that's probably mainly because I use email notifications. I could connect Raygun to pagerduty or something to have more options.

There are many integrations available, but I would like to have more features in some of them. Example: the integration with Azure DevOps is nice, it can help you create bugs from error reports in Raygun. But the sync is one way - it would be nice to have Raygun pull information back from the issue (like when it is resolved, and what release it is fixed in).

The pricing is fair, but a bit hard to estimate and understand. I can see that it makes sense though, I pay for things that increase cost for Raygun. Review collected by and hosted on G2.com.

Integration with Slack is very helpful, allows for instant feedback Review collected by and hosted on G2.com.

The dashboard is a little unclear, in terms of navigating and finding related errors Review collected by and hosted on G2.com.

Real time monitoring, breadcrumbs on errors. Review collected by and hosted on G2.com.

Performance impact on node "instrumentation" Review collected by and hosted on G2.com.

Bugs are reported to the point in the services. Review collected by and hosted on G2.com.

Sometimes unwanted or casual bugs occurs many times Review collected by and hosted on G2.com.