Before we had raygun, we would receive several emails telling us about issues that were lacking in detail so it took several emails back and forth to even diagnose the issue before we could even think about fixing it. Now, we are alerted as soon as an error occurs and we can be working on the fix before a user even contacts us about it. It has been a game-changer. Review collected by and hosted on G2.com.

There really isn't much in terms of downside. As long as you set things up properly, which is fairly straightforward, you should have no major issues. It has been a great experience. It's hard to believe we ever functioned without raygun. Review collected by and hosted on G2.com.

Analytics about error frequency are pretty good and give good insights. That is the tool we usually use the most. so that we understand not only what is happening but also how frequently and who is being impacted by that. Review collected by and hosted on G2.com.

Error grouping is sometimes inaccurate leading to missed errors. We rely on slack notifications to be aware of any issue and we sometimes get notifications lacking context, some others with names of past errors so you have to go top the actual error to see if it is a duplicate or not. That led us to stop relying on notifications and having to go to the platform to check errors, which is time-consuming and hard to keep track of which errors we have already acknowledged. Review collected by and hosted on G2.com.

The capability to track real users in a real environment. The breadcrumb feature is really nice and the alerts when an error appears in a short time allow you to react immediately. Review collected by and hosted on G2.com.

The reporting tool can be a bit short in some situations. Review collected by and hosted on G2.com.

The entire HTTP request information and the entire stacktrace Review collected by and hosted on G2.com.

For Windows Services misses the which is the name of Windows Service (the information of the .dll or .exe that is sending the report). Could also have some kind of shortcut to build a CURL request to allow the developer to simulate the same request without needing to copy manually to POSTMAN or CURL. Review collected by and hosted on G2.com.

We are running on a non-standard framework and yet I was able to easily integrate the Raygun service with error logging in my app stack. Review collected by and hosted on G2.com.

Some errors are not easily debugged - the stack traces seem to show more about the Raygun SDK than the application. Review collected by and hosted on G2.com.

Live error tracking of our website, user tracking Review collected by and hosted on G2.com.

Login can be a bit clunky and then following to the lined error report Review collected by and hosted on G2.com.

It's very easy to search and narrow down what you are looking for. If I'm troubleshooting something in real time, the errors bubble up to the top and are very easy to find as well. Review collected by and hosted on G2.com.

If the same error has occurred across different users or other log sources, it aggregates the errors into one instance, which can make it a little more difficult to find the exact instance Review collected by and hosted on G2.com.

The easy way in wich my team and I can track the issues of s certain proyectos, owner of the issue andcomment how it was solved Review collected by and hosted on G2.com.

In slack integration We have turn off the repeat error Option but with airflow it still throws repeated issues Review collected by and hosted on G2.com.

Easy interface and set up. Good high-level dashboard. Review collected by and hosted on G2.com.

Updates are rare and slow to come. Team doesn't look at the feature request board and openly pushes back on requests -- one example about user defining the health score criteria. Review collected by and hosted on G2.com.

It is easy to query for application errors. Review collected by and hosted on G2.com.

It doesn't fully support serverless yet. Review collected by and hosted on G2.com.