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
While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...
For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...
As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...
The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...
The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...
Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...
Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...
Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...
In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ...
Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...