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.
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.)
DevOps is a complex, multi-dimensional topic. It is context-sensitive. Those who attempt to learn about and implement DevOps bring their roles and cultural perspectives to the process. Diversity of opinion and expertise can be an important advantage. However, it can also lead to friction and contention in developing DevOps consensus.
It sucks to spend a long time building an app then get complaints about slow loading pages. You don’t know which pages the problems occur on, let alone the environment. So, software performance problems stay elusive, and linger on in your app, causing havoc for end users and your bottom line.
Having worked closely with software developers for almost a decade, I’ve noticed some common traits amongst them. Technically minded people think about problems in different ways. I’m often stunned how I could miss such an obvious data point or edge case when discussing product changes with people who have a far greater technical mind than myself.
