When you’re building software, there’s so much to think about — from bugs to how fast your application loads. We’ve got something new to help your development team build better, faster experiences for your users, in less time. Today, we’re releasing Raygun Application Performance Monitoring (APM) for .NET, a new way to visualize and understand your application’s performance on the server-side.
Have you ever had responsibility for an application and been the last to know about an outage? I have, and it’s terrible. You go to check your phone in the morning over coffee, after waking up, and you see a flood of missed calls and tons of emails. Customers are angry. Your boss is demanding to know what’s happening. Even the company’s executives are involved. How did this happen?
Monitoring remains a critical part of managing any IT system, while the challenges associated with monitoring microservices are especially unique. An example is how traditional monolithic systems, deployed as a single executable or library, have different points of failure and dependencies than those deployed with a microservices architecture.
You work on your software’s performance. But let’s face it: production is where the rubber meets the road. If your application is slow or it fails, then nothing else matters. Are you monitoring your applications in production? Do you see errors and performance problems as they happen? Or do you only see them after users complain? Worse yet, do you never hear about them? What tools do you have in place for tracking performance issues? Can you follow them back to their source?
In an ideal world, bugs would never reach production. But, software errors are an inevitable part of a developer’s life. Java debugging tools exist to help us resolve errors faster, so we can get on with doing what we do best. This list of Java debugging tools will help you evaluate your options quickly so you can find the best for the job.
The Raygun platform is designed to surface as much actionable information about errors so, as a developer, you not only fix them quickly but gain context into what causes errors in the first place. Today we’re announcing a new feature for both Crash Reporting and Real User Monitoring: Crash by device. This new feature helps mobile developers understand which devices cause the most crashes, so replicating errors becomes easier.
Raygun Crash Reporting has supported the Java Framework since we launched. As a Java customer, you’ve always been able to catch errors pre and post-production, receive alerts, and provide one source of truth for errors on your whole team. Now, Raygun provides full feature support for Raygun4Java. Java customers now have access to all our favorite Raygun features, like Breadcrumbs, offline support, web service support, and sensitive data filtering.
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.
