If you need to replicate a user error, you’ll know how difficult it can be to pinpoint the cause. Usually, you’d look at the stack trace or ask the user themselves. However, that’s a lot of guesswork, especially if the stack trace is obfuscated. We’ll show you how to replicate the error faster using Crash Reporting’s Breadcrumbs and the Real User Monitoring Sessions feature.

Last April, we launched a new feature called Custom Dashboards allowing teams to sort and view data from Raygun Crash Reporting, Real User Monitoring, and Application Performance Management. It was built as an upgrade to our Legacy Dashboard, offering better visualization, customization, and navigation.

We are excited to announce our recent support of .NET Standard 2.0 and ASP.NET Core 2 applications for Raygun Crash Reporting. The update is for developers needing to target the .NET Standard 2 APIs. Our new provider targets both .NET Standard 1.6 and .NET Standard 2.0, so it can be used with both .NET Core 1 and .NET Core 2 applications. At the time of writing, it is just the .NET Core provider and ASP.NET Core provider that are .NET Core 2 compatible.

Complex distributed systems run just about every service imaginable. Healthcare systems that monitor patient health, security systems, and financial systems are all mission-critical. Downtime, or lack of availability, loses money and can even put lives at risk. These systems must be monitored. Many measurements are useful to keep systems running with as little downtime as possible. One of those is Mean Time To Recovery. (MTTR.)