Raygun Reviews

View detailed error information and good UI

Currently, no bad points have been found

Raygun helps to solve serious errors quickly

What I love most about Raygun is its ability to provide real-time alerts and notifications, so I can stay on top of any issues that may arise and address them immediately. This has helped me to maintain a high level of customer satisfaction and ensure that my applications are running smoothly at all times.

One issue that some users may encounter with Raygun is the cost of the software. The pricing structure can be a bit complex and may be cost-prohibitive for smaller businesses or startups with limited budgets. Some users have also expressed frustration with the lack of customization options for certain features, which can limit the flexibility of the software for some use cases.

One of the primary problems that Raygun is solving is helping businesses to identify and diagnose errors and performance issues in their applications quickly. Raygun's real-time error tracking and reporting features allow businesses to identify and prioritize errors based on their impact on the application's overall performance and user experience.

Immediate notification and visibility for all users of exceptions found by raygun, visibility as an MS teams alert

Not to many downsides to be honest, we get a few flags during synthetics but we have upskilled enough as to know when genuine alerts are raised

Unknown issues in our api services that are immediatly brought to our attention for the dev team to work on.

We have been using Raygun for several years and it has been brilliant.

We have Raygun set up in all of our dev environments and it has been easy to setup and it's our "go-to" tool if an error occours.

It has been the first thing we implement in all of our solutions for error tracking.

My only downside to Raygun is that I have noticed that when looking at a particular exception with a large amount of exceptions it can be hard to find a specific exception - would be nice if there was a graph similar to the one on crash reporting main screen that the user can use to select specific time frames to see error count rather than going back to the crash reporting main page to change the date time.

Raygun has allowed us to find exceptions easier, find all the information of a stack trace and monitor how well a release/ solution is doing by monitroing the amount of new/existing exeptions being throw.

What I like the most is that as a team we can see the app exceptions when they occur, and quickly decide if we need to make the fix.

I have been using raygun for about 1 and a half years and everything is perfect so far.

Bugs that found their way through production, we detect them as they occur and take action to solve the issues.

I like the UX/UI to see the issues in the endpoints, the way how to raygun split the applicants, apply filters, create dashboards, and most important the stack trace of the issue.

I would like to track the server errors logs level because for instance when something goes wrong I need to check AWS cloud watch and then raygun to figure out where the issue is, it could be excellent to have these log only in raygun

Detect potential issues in my endpoints, generating a report where it shows the occurrences and numbers of users affected, also the details of each issue with helpful information to solve the issue as soon as possible.

The .NET integration is great. This tool helps us track, find and repair bugs quickly and easily.

Sometimes the grouping is off - we get errors reported on one URL that are occurring in a different place but tripping a similar exception.

We just changed our whole stack from ASP .NET to .NET6 and raygun has been incredibly helpful in helping us track the new bugs introduced by the framework change. Turns out, .NET6 is so much faster, we have a whole new set of errors to find and fix.

I have fairly simple needs but getting a fullstack trace for winforms makes life super easy.

I would like slightly more control over how excessive error throttling works. I love that it stops logging to avoid high bills but i'd like to set that threshold

Testing new software during development RayGun is a lifesaver at catching unexpected errors. In the real world, getting detailed info on unhandled errors often means i have fixed a problem before the client even knew there was an issue.

It is so helpful to see what exceptions have been occurring, but logging these on clients' computers is nowhere near as effective as seeing them collated in Raygun in almost real time.

The interface is clean and effective and to the point - easier to use than Microsoft's Application Insights or similar.

I don't understand the difference between marking errors as "Resolved" or "Ignored" as they both seem to behave the same - if the error re-occurs, they pop the error back in the "Active" tab.

Instant visibility over all errors, and how often they have been occurring, has brought the information to me, and in a nice collated table, instead of my having to log into clients' servers and retrieve the information and collate it.

Consequently, we have been able to jump on significant errors before users could even log a call with us.

I have used the product for several years across several websites, and I specifically like the following:

- How easy it is to set up

- The automatic alerts work perfectly

- Slack integration is nice

- The documentation provided is great

- Interactions with customer support have been easy and prompt over the years.

I wish Raygun supported log streaming. Seems like a natural addition to the existing product lineup.

I primarily use Raygun for error tracking and notification.