Bugsnag, a SmartBear company, announced new error monitoring capabilities to help drastically simplify application development, enabling organizations to drive greater business results with an improved user experience.
The new features support code ownership and accelerate the debugging process for better collaboration and team alignment. Recent data shows that when engineering teams grow to over 100 employees, debugging code becomes increasingly more complicated, making it more difficult to maintain a higher stability. Bugsnag’s new features eliminate that risk and complexity, especially for large engineering teams, allowing them to deliver a better, more stable user experience.
“Most apps have a variety of engineers, including separate engineering teams, working from a single code base. When something goes wrong, all engineers are alerted about the software bug. They then have to figure out where the error occurred and who is responsible for fixing it, which is a cumbersome and inefficient process,” said James Smith, SVP of the Bugsnag Product Group at SmartBear. “Bugsnag’s new features eliminate this guesswork and deliver true code ownership so engineering teams can easily identify, own, prioritize and remedy bugs. When organizations can quickly stabilize apps, the customer’s digital experience improves significantly, ultimately helping to boost critical business outcomes. In addition, engineering teams become more cost- and time-efficient, freeing them to take on other projects and build new features.”
Bugsnag’s latest features allow customers to:
- Gain visibility beyond crashes in mobile apps with NDK Stack Frames and iOS app hangs: To mitigate Application Not Responding errors (ANRs), Bugsnag has introduced NDK stack frames. The new NDK stack frames, along with the existing JVM stack traces, provide complete visibility into the section of code that was running when an ANR occurred, allowing engineers to easily investigate and fix ANRs. Bugsnag provides visibility into iOS app hangs, with complete diagnostics including stack traces and breadcrumbs, to help correct both fatal and non-fatal iOS app hangs.
- Drive code ownership and increase team alignment with multiple issue trackers: Bugsnag’s new features support code ownership with automatic error alerts, sending notifications about bugs to the specific team that owns the problematic part of the codebase, regardless of the type of tracker they use. This ensures that only the correct team is made aware of a bug, rather than sending error alerts to all engineering teams, which makes it difficult to determine which team should fix a problem.
- Use powerful diagnostics to fix errors with advanced filterable breadcrumbs, jailbroken device detection, and app crashed on launch identification: New capabilities expedite the process of identifying and correcting bugs by giving engineers the ability to search and filter the user interaction breadcrumbs collected for each error. Teams can select the type of breadcrumb or search with keywords. As a result, engineering teams can filter by specific user actions or network requests to investigate what the user was doing in the run up to the error. With an updated average device state analysis, engineering teams can quickly understand if the application was being used on a jailbroken iOS or rooted Android device when the error occurred. For multi-platform applications, such as React Native and Unity, engineers can now easily see if each error is affecting iOS or Android users. There are also new diagnostics to help engineers Identify whether a crash occurred while the app was launching and filter by this error detail to prioritize fixing these high impact crashes.
- Streamline error prioritization with enhanced snoozing and Microsoft Teams integration: Bugsnag enables engineering teams to also snooze errors until they impact a customized number of users, so teams are only alerted once a bug causes a significant enough problem. The update also includes a new integration with Microsoft Teams, allowing engineers to receive alerts in Teams when Bugsnag identifies errors. Like the snooze options, these alerts are also fully customizable, making it easier for engineers to prioritize the most serious errors.
The Latest
Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...
For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...
Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...
Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...
For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...
New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...
Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...
When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...