Get the most recent info and news about bugsnag on HackerNoon, where 10k+ technologists publish stories for 4M+ monthly readers.

bugsnag

MuukTest, an AI test automation platform, is excited to announce the launch of TestXplainer, a generative AI tool that empowers everyone involved in QA by translating data into clear and simple test strategy information that is accessible to all.

Redefining AI Software Testing: MuukTest Unveils TestXplainer

In May, about 17,000 SIM cards were deactivated in two states using the ASTR system. Facial recognition software also reportedly helped prevent about 10,000 incidents of voter fraud during a village election later the same month. The ASTR system identifies ...

Facial recognition tool nets over 6M SIM card fraudsters in India in 6 months

The Software Testing and Quality Assurance course is a vital component of modern software development, aimed at ensuring that software applications meet the highest standards of reliability ...

Software Testing and Quality Assurance course | H2kinfosys

Note: At Cybernews, we regularly test and research antivirus software to update this list with products that are of the highest quality. Choosing the best antivirus might seem challenging at first. There are so many options offering a variety of different ...

Best antivirus software for 2023

For instance, incorporating quality assurance processes at each phase of the software development lifecycle reduces the rate of defects at the later stages of software development. This eventually reduces the need for rework and minimizes the development ...

Beyond Billboards: Why Quality Software Speaks For Itself

But how do you know you’re getting the sound quality you deserve? In this article, we’re going over how to perform a successful headphone test, uncovering the ultimate guide to evaluating ...

The Ultimate Headphone Test for Sound Quality

It helps managers prioritize projects among a long list of goals. Portfolio management software aids managers in keeping a high-level view of which projects are meeting the needs of the ...

Best Project Portfolio Management Software (2023)

With over 22 years of experience in software testing and quality assurance, Testhouse is sure to help you deliver the best quality applications for Desktop, Mobile and the Web. By conducting functional, security and performance testing, this provider is ...

Pentest tools to improve your company's security posture

Our client, a medium sized IT company based in Somerset specialises in Business Intelligence, SAP software, Enterprise Performance Management, and related planning as well as reporting systems. We currently are searching for an ambitious and dynamic ...

Business Analyst (SAP BI and Analytics) (C955) – Western Cape Cape Town

Apple said that the testing protocol used by L’Agence Nationale des Frequences did not take this feature into account. The company issued a software update that will become broadly available to ...

Apple updates iPhone 12 software to address France’s radiation testing

3 Market Competition, by Players 3.1 Global Software Quality Assurance and Testing Service Revenue and Share by Players (2019,2020,2021, and 2023) 3.2 Market Concentration Rate 3.2.1 Top3 Software ...

Software Quality Assurance and Testing Service Market Trends Research Report [2023-2030] | 118 Pages

The best antivirus software can help keep your Windows computers ... Find out more about how we test, analyze, and rate. 1. Norton packs in everything but the kitchen sink Norton's antivirus ...

The best antivirus software 2023: Free and paid options

At Verity Software, our comprehensive Software Testing Training program covers a wide range of topics and practical skills, ensuring you are well-prepared for a successful career in software testing. Here are some key aspects of our training:

Mastering Software Testing with Verity Software: Your Path to Success

Tesla has managed to greatly improve the camera quality of its existing electric cars with HW3 through an over-the-air software update. Lately, Tesla has been flexing its capability to improve its ...

Tesla manages to greatly improve camera quality on its cars through software update

: NetEngine’s business is based on providing high-quality stable software to its clients, however, developers lost visibility into software when it was delivered to customers and deployed to production. The team was only alerted of errors from customer complaints, leading to an unpleasant experience for developers and customers. Challenge : Using Bugsnag, NetEngine has visibility into production errors and can often preemptively fix errors before customers are aware of them. Bugsnag allowed NetEngine to fundamentally change their business model to offer an ongoing contract with clients for software management, and provide an overall better customer experience. Results NetEngine’s business depends on creating high-quality software, but without error monitoring, critical bugs went unnoticed. NetEngine creates web and mobile products for a range of industries, such as travel, health, recruitment, local government, and non-profit. They create Ruby on Rails and JavaScript web and mobile products using proven lean and agile methodologies. NetEngine’s business depends on developing great software solutions for their clients, making it imperative to deliver stable, high-quality software. However, the engineering team had no error monitoring tool in place, which meant bugs in production went unnoticed until a customer complained. “When a customer finds a bug, they are irritated as is, and they obviously do not want to get invoiced for buggy software,” mentions Bruce Stronge, cofounder and CEO of NetEngine. After a disgruntled customer notified the team of an error, a developer had to try to replicate it, digging through log files, or even contacting the customer to try to piece together what occurred. “Troubleshooting bugs with this process would take an entire day for 2 or 3 of our developers,” states Stronge. “In addition, we would have the customer calling every hour to know if the issue was fixed. All in all, this posed a lot of stress and dissatisfaction for all parties involved, and it was definitely not the type of experience we want to deliver.” Improving customer relationships with proactive error monitoring NetEngine sought out an error monitoring tool that would let their developers proactively address bugs, helping them deliver quality software in a timely manner, and therefore create long-lasting relationships with their clients. NetEngine chose Bugsnag as their error monitoring tool because of the ease of implementation and use. “Because Bugsnag is so affordable and easy to set up, we can use it for every project and not just the large, high-budget ones. The moment our customers have a pilot, they have error monitoring for it.” — Bruce Stronge, Cofounder and CEO Thanks to Bugsnag, NetEngine’s developers save valuable time when addressing errors. “We can fix bugs in 30 minutes instead of 2 days,” comments Stronge. “Our customers hardly see any bugs, because we fix them right away.” Using Slack and TriggerApp integrations to improve efficiency Bugsnag’s Slack integration is another highly used feature at NetEngine. It lets engineers know immediately when an error occurs, and the impact of it. “Each of our 25 developers now saves 10 minutes every two hours, because they don’t have to search for errors and then alert the rest of the team. We get automatically notified when errors occur,” mentions Stronge. “Another powerful integration is with our project management tool TriggerApp, where tasks are now automatically created and assigned from Bugsnag - a huge efficiency creator”. Bugsnag has not only allowed NetEngine to save valuable time when troubleshooting exceptions, but they are also able to maintain an ongoing contract with their clients, which is seldom heard of for project-based consulting companies. “We are easily able to sell the benefits of Bugsnag to our clients,” says Stronge. “By having a maintenance contract with our customers, we maintain ownership of a product, and can more easily find and fix any issues that arise.”

How NetEngine Tracks Critical Bugs Using BugSnag

Cómo NetEngine realiza un seguimiento de los errores críticos mediante BugSnag

Comment NetEngine suit les bogues critiques à l'aide de BugSnag

NetEngine BugSnag का उपयोग करके महत्वपूर्ण बग्स को कैसे ट्रैक करता है

NetEngine が BugSnag を使用して重大なバグを追跡する方法

Como o NetEngine rastreia bugs críticos usando o BugSnag

Cách NetEngine theo dõi các lỗi nghiêm trọng bằng BugSnag

NetEngine 如何使用 BugSnag 跟踪关键错误

: Yelp recognized that its previous crash reporting tool provided inadequate search functionality for developers and caused a slow cold start Android app launch for users. Challenge : Yelp has achieved a 99.98% stability target using Bugsnag to improve its app stability. As a result, Yelp fulfills its promise of a dependable and fast user experience, which is reflected in its impressive Google Play ratings. Results Yelp strives to deliver crash-free mobile experiences Yelp, a popular local-search platform that connects millions of consumers with great local businesses, is tied directly to the consistent delivery of a stable and expeditious mobile app experience. To live up to expectations, information must be instantaneously available to users in their moment of need, which means app crashes are completely unacceptable. As Antonio Niñirola, Yelp’s Core Android Engineering Manager, explains, “If an app crashes twice, I’m going to uninstall it because it’s a bad app. I don’t care which app it is. Yelp aims to never be in that position.” Visibility into crashes helps maintain strong user experiences As the Android team has grown at Yelp so has the need for a stability monitoring solution. While the original team was small and able to work together to figure out why a crash occurred, today’s team and development process have grown to approximately 50 contributors for every weekly release. Stability and crash monitoring are critical for managing this speedy release process. While Yelp started with an internally developed tool, they quickly realized it was difficult to maintain and wasn’t worth the investment. They switched to Crashlytics but encountered challenges which led them to start exploring other tools. “We like to have as low a cold start as possible when the user starts to use the app for the first time,” according to Antonio. Bugsnag delivers results through the stability score, search, and integrations Yelp’s Android team was the first team within Yelp to select Bugsnag as its stability monitoring solution after evaluating it against Crashlytics. The iOS and web teams have subsequently adopted Bugsnag after hearing about the numerous benefits. The Bugsnag Releases dashboard is used to see adoption numbers and the stability score for each release which gives a clear understanding of its health. Since the Android team does an alpha release every day and a beta release every week, the ease of identifying problematic releases is key to their success. “Bugsnag makes it easy to receive an alert whenever something goes wrong, and is extremely quick. Alerts allow triage to occur without delay, and Bugsnag has no negative impact on app starts. Bugsnag’s error libraries are completely open source, which allows us to actually look at the code.” — Antonio Niñirola, Engineering Manager Antonio also finds that the strong search functionality further accelerates the debugging process. When a bug is assigned, developers can easily find the information they need and Bugsnag provides more intelligent error grouping than competitor products. With Bugsnag’s integrations to systems like and Splunk, Yelp benefits from seamless information sharing across systems. For example, release information from Bugsnag is pulled into Splunk and merged with other internal metrics and data sources in order to make data-driven decisions that impact the broader business. Slack Antonio and his team appreciate the strong feedback loop to Bugsnag. “Over the years, we’ve communicated a lot with the Bugsnag team, and a lot of our feedback has been addressed,” Antonio states. Yelp reduces the number of crashes through preemptive detection Bugsnag is now part of Yelp’s release management process, and the stability score is the main metric used to determine success in weekly releases and staged rollouts in Google Play. As a result, Yelp updated their stability target from 99.7% to 99.98%. They also reduced their APK size by approximately 50 percent, thanks in part to Bugsnag’s small library size. Since adopting Bugsnag, the Android team has noticed a decrease in the number of crashes reported by their beta group in Play. Yelp attributes part of their release process improvements to the implementation of Bugsnag and their ability to find crashes before they release. Google “I would say that crash reporting is one of the main things you should have in your app. It’s super important to have visibility, especially within a large organization like Yelp. Detection is 100% faster when you have crash reporting.” — Antonio Niñirola, Engineering Manager Also published . here

Yelp's Mobile App Stability Soars to 99.98% with BugSnag

La estabilidad de la aplicación móvil de Yelp se eleva al 99,98 % con BugSnag

La stabilité de l'application mobile de Yelp monte à 99,98 % avec BugSnag

बगस्नैग के साथ येल्प के मोबाइल ऐप की स्थिरता 99.98% तक बढ़ गई है

Yelp のモバイル アプリの安定性が BugSnag で 99.98% に上昇

A estabilidade do aplicativo móvel do Yelp sobe para 99,98% com o BugSnag

Độ ổn định của ứng dụng di động của Yelp tăng vọt lên 99,98% với BugSnag

Yelp 的移动应用程序稳定性借助 BugSnag 飙升至 99.98%

: Reliability is Shopify’s top priority for its 300 thousand-plus daily users. Without the ability to gauge the impact of errors, Shopify engineers had limited visibility into user experience, and oftentimes, customers contacted them with problems before errors were discovered. Challenge : Using Bugsnag, Shopify engineers are aware of errors significantly faster, can more easily replicate errors, and can proactively see the effects of their code. Trend analysis helps engineers understand common causes of errors and mitigate future problems. Results Before error monitoring, ensuring reliability for Shopify’s worldwide customer base was tedious, time-consuming, and inefficient. Shopify develops e-commerce software for more than 377,500 online stores and retail point-of-sale systems around the world. For Shopify’s engineering team, the top priority is to maintain reliability for each customer worldwide. However, that process used to be very time consuming and tedious for Shopify’s software engineers. “Troubleshooting used to be slow and unpleasant, requiring us to invest a lot of time digging through logs and piecing together information from multiple sources,” states Blake Mesdag, Sr. Developer for Shopify’s CI Infrastructure team. Trend analysis is another great way to mitigate potential exceptions, but before error monitoring was implemented, it was difficult to build a complete picture of errors over time. Without spike notifications, alerts that indicate a sudden increase in the occurrence of an error, bugs would escalate and affect customers, requiring them to reach out to Shopify so they could be fixed. Preempting Support Calls With Increased Visibility Into Errors It soon became apparent that a more proactive way of addressing errors had to be implemented for all of Shopify’s development process. “Without error monitoring, you’re flying blind - there’s almost no point if you can’t see what you’re doing right and wrong, and you can’t make any informed decisions,” says Mesdag. After considering several options, Shopify chose Bugsnag for automatic error monitoring of their entire tech stack. Shopify’s developers, across 20-30 teams, can now proactively see the effects of their code and identify and troubleshoot errors before they impact merchants. “Overall, Bugsnag has helped me become more confident in the code I ship, which in turn helps me ship faster” — Blake Mesdag, Sr. Developer Before Bugsnag, Shopify software engineers could not proactively see what errors were occurring and would have to wait for customers to reach out with problems. They would then have to dig through logs to find an exception ID, and then use that to find it in the exception tracker. “Bugsnag surfaces all of this information in one place, and it tells us exactly what caused the error,” states Mesdag. “There is a lot less search involved with Bugsnag, and the overall process of troubleshooting bugs is significantly more pleasant.” Using Trend Analysis to Mitigate Future Errors With Bugsnag, Shopify developers can also analyze trends on exceptions. This helps them understand common factors that cause failures so they can take a proactive approach to mitigate these in the future. Trend analysis is powerful for the infrastructure team to diagnose if specific machines are causing more issues than others. In addition, by having spike notifications, it becomes much easier to pinpoint errors that are quickly escalating, prioritize them, and get them fixed much faster.

How Shopify Uses BugSnag to Service Over 377,000 Online Stores

Cómo Shopify usa BugSnag para dar servicio a más de 377 000 tiendas en línea

Comment Shopify utilise BugSnag pour desservir plus de 377 000 boutiques en ligne

शॉपिफाई कैसे 377,000 से अधिक ऑनलाइन स्टोरों को सेवा प्रदान करने के लिए बगस्नैग का उपयोग करता है

Shopify が BugSnag を使用して 377,000 以上のオンライン ストアにサービスを提供する方法

Como a Shopify usa o BugSnag para atender mais de 377.000 lojas online

Cách Shopify sử dụng BugSnag để phục vụ hơn 377.000 cửa hàng trực tuyến

Shopify 如何使用 BugSnag 为超过 377,000 家在线商店提供服务

: As Namely’s HR offerings and engineering team scaled, it became evident they needed to standardize how troubleshooting software bugs was done. Until then, each engineering team had its own process, and the previous tool they used did not support many of the coding languages used at Namely. Challenge As of early 2017, all of Namely’s engineering teams use Bugsnag to troubleshoot errors. This has allowed them to unlock several benefits, such as becoming aware of bugs and understanding the root cause 50% faster, and improving their customer’s experience by continuously keeping application stability as top of mind. Results: Namely was looking to standardize the way they addressed errors across all engineering teams in order to remove complexities and save valuable time. Namely is an all-in-one human resources platform for businesses of all types. As the number of Namely’s HR products increased, so did the number of engineering teams and the different coding languages they used. “Once you move away from a monolith and into a microservices framework you add significantly more complexity to the process,” states Teresa Dietrich, CTO of Namely. “We wanted to remove that complexity by standardizing the way we did error monitoring across all of our teams and languages.” Namely’s previous error monitoring tool was mainly built for , and did not support other key languages like Core, which is used for Namely’s core product, Payroll. The lack of language support meant many teams did not have an error monitoring tool in place, and relied on customers flagging errors via support tickets. On the other hand, those who did use the previous tool had limited ability to track errors, and information was scattered throughout multiple applications. Ruby .NET One error monitoring platform for all frameworks As of Q1 2017, all of Namely’s projects and engineering teams use Bugsnag for error monitoring. Since then, they have reaped countless benefits. Aside from being able to use Bugsnag for all applications regardless of language, they also now have support for SAML and SSO, two very important protocols given the amount of personal information that Namely handles for their customers. Also, unlike their previous tool, engineers can use precise filters on each project’s error data, allowing them to sift through the noise and only get notified of bugs that matter. “We get information about a bug at least 50% faster.” In general, Bugsnag has allowed Namely to monitor for errors more efficiently and troubleshoot bugs significantly faster across all engineering teams. Identifying and understanding an error’s root cause is also faster with Bugsnag. “We are no longer going into three different systems to get information about a bug,” says Robert Ross, Core Services Software Engineer. “We can skip logs and NewRelic and get everything in one place.” Improving the customer experience with quality software In addition to improving how troubleshooting is done, Bugsnag has allowed Namely to further focus on their customer’s experience. Engineers are not only shipping products with even higher stability than before, but they can also fix issues and respond to customers much faster. “I’ve heard several of our engineers recommend Bugsnag to others,” says Dietrich. “That on its own is a testament of how much value they see in Bugsnag. It significantly alleviates the pain of troubleshooting errors.” “We are working on more bugs than before and are able to identify them much faster.” — Teresa Dietrich, CTO Also published . here This story was distributed as a release by Bugsnag under HackerNoon’s Brand As An Author Program. Learn more about the program here: https://business.hackernoon.com/brand-as-author

How Bugsnag Empowers Namely's Engineering Team with Error Troubleshooting

: Gusto’s business is designed around empowering a better life for all employees through their work, but existing bug-fixing processes didn’t fit this goal. The process of finding and fixing bugs was complicated, tedious, inefficient, and all-around unpleasant for Gusto engineers. Challenge Gusto redesigned its bug-fixing process around the idea of code ownership. Using , engineers have visibility to errors that occurred in the code they wrote, clear indicators for the impact of each error, and the resources needed to diagnose and resolve errors quickly. Results: Bugsnag As Gusto scaled, their process for identifying and fixing errors became a burden on the engineering team Gusto is a comprehensive HR, payroll, and benefits platform for small and medium businesses. Gusto has an extensive human resources platform and more than 90 developers who diligently work on creating and maintaining its multiple applications, like payroll, health benefits, payments, risk checks, and others. As each of Gusto’s applications scaled and the number of customers grew, their engineering teams identified that troubleshooting bugs was becoming a very tedious and inefficient process for the developer assigned weekly to that task, whom they call the Viking Master. The Viking Master would halt any other priorities and solely focus on identifying and fixing bugs. Given how much code was being pushed to production, there was a lot of noise generated when it came to error notifications. Many times, the errors the Viking Master was addressing were lines of code they hadn’t written, making it even more complicated when replicating and fixing errors. The Viking Master had to spend countless hours figuring out which errors to address first, digging through logs, and reaching out to other engineers to get the full context, just in time for a new Viking Master to start from square one the following week. Creating ownership with increased visibility into errors Eddie Kim, CTO and co-founder of Gusto, knew this was not the kind of experience he wanted for Gusto’s more than 90 talented developers. To better match their company’s value of empowering people to do their best work, Gusto sought to improve the necessary task of troubleshooting errors and make it a much more enjoyable and less time-consuming process. “Whenever an error occurs, each application team gets immediately notified via Slack, where we show pertinent information about the exception and which developer committed the code.” -Eddie Kim, CTO and cofounder Reducing support tickets with streamlined troubleshooting workflow Another efficiency created by the Developer Experience team was using Bugsnag for workflow purposes. Once an error is identified, it is useful for the team to know which errors are being worked on and by whom. This ensures that no important issues fall through the cracks and that there are clear next steps as to who should be fixing what bugs. Even though the Developer Experience team is continuing to roll out more efficiencies to the error troubleshooting process, Bugsnag has already allowed them to realize some initial benefits. Mean time to resolution has decreased and all engineering teams can now enjoy smoother deploys that allow them to address errors before they escalate. “Bugsnag is a central tool that enables us to create ownership mentality for all software engineers.” -Eddie Kim, CTO and cofounder By enabling developers to more easily identify and address errors, Gusto can quickly iterate and improve their software’s performance. This leads to more robust and faster background job processing systems, such as the amount of time it takes for their customers to run payroll or file taxes. As a result, Gusto offers a better customer experience leading to fewer support tickets and increased customer satisfaction. Also published here.

How Gusto Makes Bug Fixing Enjoyable With Bugsnag

Hello, and welcome to part two of the Bugsnag Beginners Series! We will cover the error details page and how it can be used to maximize error debugging in your Bugsnag Dashboard. We’ll start by going over how error details heading information is organized, followed by what different pivots mean, how the status box works, where to find diagnostic data, and lastly how to create custom filters using your error’s metadata. Let’s start by clicking into an error from the Error Inbox, bringing us to the error details page. Error Details Heading An error’s heading information is a great place to start the debugging process. At the top of the heading is the error class, which will appear alongside the blame frame pulled from the error’s stack trace. On the line below is the error message that was given by the exception when it occurred. The bottom two lines display general information about the severity and frequency of the error, as well as the grouping logic that was applied to that particular class of errors. : Error details data will vary by platform. Note Pivots Transitioning to the next topic, let’s discuss the different list views available within a group of errors, which are known as pivots. By default, the error details page displays a class of error events based on how recently they occurred within the app; however, by selecting different pivots at the top of the page, a variety of segmented errors can be explored. Aside from the aforementioned event pivot, the segmented list views are as follows: users impacted, release stages the error was seen in, which release version the errors occurred in, features flagged within the error, and device details such as OS and model. Custom pivots also can be created for further segmentation, such as shutter speed, focal length, or VIP customers impacted, as seen below in our camera app. Status Box The status box seen on the left-hand side of the error details page contains three useful sections. The first at the very top is specifically designed for quick triage by assigning various errors a workflow status. For more on workflow statuses, check out . The next section in the status box is the histogram of the error class, labeled as the Trend. This displays the app health in relation to that error class within the currently selected time period, displaying up to 60 days of historical data. The final section in the status box is the average device state. Here, device-specific information –such as foreground duration, memory states, and whether the device was jailbroken – can be found. Part One of the Bugsnag Beginner Series Note: Average device state will only appear for mobile app projects. Diagnostic Data By clicking into the error, diagnostic data will be displayed to help better understand what steps the user took before the error occurred. The first key diagnostic that appears is the full stack trace, as well as an option to view the raw data and the threads. Next to the stack trace are the breadcrumbs, where the user clicks and screen views can be seen. Going further right, app and device state is displayed to provide device specific information that may have caused the error. Lastly, user and feature flags can be seen if previously configured, which add an extra level of granularity to the debugging process. Custom Filters From the diagnostic data display, custom filters can be created by clicking the index button found to the left of any of the metadata. Custom filters will be displayed under the Summaries box found to the bottom left of the page, and as queryable custom attributes within the Error Inbox. By default,10 custom filters can exist within a Dashboard – so create with care. If a custom filter was added by mistake, it can be deleted from Project Settings by clicking Custom Filters. We look forward to seeing you In part three of this series, where we’ll cover the Releases page and the Stability Center. Also published . here

Bugsnag Beginners Series: Part 2 - Error Details

So, whether you’re logging into the Bugsnag Dashboard for the first time or have already created several projects, this series will help you develop a strong foundation for using Bugsnag efficiently and effectively. Let’s kick things off by talking about one of the essential pages in Bugsnag, the Bugsnag Inbox. This page houses all of an app’s crash data and can be used to visualize overall app health within a customizable timeline. The grouping logic built into Bugsnag uses the underlying root cause of a crash to group exceptions as unique events. This helps minimize noise, as well as identify the most relevant crash data in the Inbox. Bugsnag displays each grouped crash with the error headline, as well as the top stack frame where the crash occurred in the app. Below the headline is the message generated with the crash, as well as when the error was last seen and first introduced. If any users within the Bugsnag project commented on the error or were assigned ownership of the bug, that can be found next to the timestamp. 1. Error headline 2. Error message 3. Last time error was seen; First introduced 4. Error comments 5. Error assignee Error Details Moving onto the right side of the Inbox, here, the crash count of each corresponding error can be found, as well as how many users it has impacted. Clicking these parameters will sort them by total count, starting from largest to smallest. Further right is the trend bar corresponding to each error’s impact within the Inbox’s current time range setting. Adjusting the Inbox’s time range can provide insight into up to two months of historical data. Next to the trend bar is the release stage that the error occurred in—Bugsnag will display both staging and production builds if the error was seen in both. Lastly, the severity of the error is reflected furthest to the right of the Inbox. Unhandled exceptions are, by default, given an “error” level of severity, and handled exceptions are marked as a “warning.” 1. Error count  2. Trend bar  3. Release stage  4. Severity level Error Triage Lastly, looking to the left side of the Inbox, errors can be assigned to various work status bins to assist triage. When an error’s status changes, it’s placed in the corresponding status bin. For example, opening an errors status assignment box by clicking the checkmark and then marking the error as fixed will move it from the “Open” status bin to the “Fixed” bin. Using this workflow will allow team members to know that the error has been actioned, as well as keep the status bins tidy. Errors can also be assigned to various team members using an error “Assigned” status or via an issue tracker integration such as Jira. Low-priority or noisy errors can be marked as “Snoozed” until they pass a customizable threshold. Lastly, for errors that don’t need to be actioned, marking them as “Ignored” will prevent them from sending notifications. Errors can also be discarded or deleted, removing an instance of the error just once or permanently, depending on the respective action. Status bins  2. Status assignment box That concludes the overview of the Bugsnag Error Inbox, as well as part one of the Bugsnag Beginners Series. Please stay tuned for the next topic, which will dive deeply into the Error Details page. See you then!

Bugsnag Beginners' Series: Part 1 - Error Inbox

Bugsnag Beginners Series Parte 1 - Bandeja de entrada de errores

Bugsnag Beginners Series Partie 1 - Boîte de réception d'erreurs

Bugsnag शुरुआती श्रृंखला भाग 1 - त्रुटि इनबॉक्स

Bugsnag ビギナー シリーズ パート 1 - エラー インボックス

Bugsnag Beginners Series Parte 1 - Caixa de entrada de erros

Sê-ri dành cho người mới bắt đầu Bugsnag Phần 1 - Hộp thư báo lỗi

Bugsnag 初学者系列第 1 部分 - 错误收件箱

As Eventbrite neared the release of their rewritten platform in React.js, they knew observability on the frontend was a problem they needed to solve. If they were going to release a dynamic, JavaScript application, they would need visibility into their product. Their homegrown solution sent errors to Splunk, but there was no clarity around which errors were problematic. CHALLENGE: Eventbrite has now implemented Bugsnag in their development and release process which has given them peace of mind. They know any bugs will be detected before they impact their entire user base. Eventbrite has also become more agile since they can release features to a subset of users, monitor incoming errors, and decide when to rollout platform wide, knowing they will be alerted swiftly of issues. RESULTS: Growth Goals and an Innovating Product Highlighted the Need for Visibility into Errors Eventbrite is an online events platform that helps organizers build, manage, and grow their events. Their software provides end-to-end online event logistics, and enables organizers to get up and running smoothly and quickly, whether they are hosting intimate gatherings or complex, large scale events. As Eventbrite solidified its platform for event organizers, they sought to grow their user base of attendees to become the destination for finding things to do. They also decided to move away from being a monolithic platform and break up their product functionality. This would allow them to offer certain services to event organizers who may not need their entire platform. These growth goals would require thinking about quality in a new way, but Eventbrite’s Frontend Platform team knew their previous system would not support their growth. “Before Bugsnag, all of our JavaScript errors were put into Splunk, and it was just a pile of errors. It was very difficult to sort through or even get any visibility into. There was no grouping or ability to see what was actually impactful, and it was mixed in with all other error messages and logs as well,” says Senna Bala who manages the Eventbrite QA team. “I would spend time trying to force people to look at errors because no one would do it proactively on their own when it’s just so difficult to do.” Since they are responsible for helping engineering produce high quality software through testing and release support, this caused a lot of problems for her team. At the time, the most common way to discover bugs was when they were reported by customers experiencing difficulty with their platform. It’s important to remember that for each user who complains about a bug, there are countless others who also experienced it and abandoned a product. Ben Ilegbodu, Principal Frontend Engineer, explains that their team was even suspicious of errors negatively impacting some of their business metrics, like conversion, but there was no way to know with certainty because of the lack of visibility into errors. Gaining Peace of Mind Enables More Agile Development at Eventbrite In the end, Eventbrite chose Bugsnag to monitor all frontend applications because of its superior user experience, like the ease with which they are able to find specific errors using custom filters. Senna and Ben agree the best thing they have gained from using Bugsnag is the tremendous peace of mind it brings their teams. “Now I can be confident that everything is going into Bugsnag, and we can actually see the number of users that are hitting a bug, the number of different events. We get such granular data that I know I can go in there and find errors that are impactful.” - Senna Bala, QA Enginerring Manager The ability to know about errors before they negatively impact customers has helped them speed up their release process. “In a sense it’s kind of like a safety net. If there’s a problem, we know we’re going to catch it. We are trying to move in a more agile way, where we can just decide to put something out to 5% of users and see how it goes. We can slowly release it out and check Bugsnag to see if there are any issues users are experiencing. This helps us move quicker since we don’t need to make sure everything is perfect before showing it to anyone, and we can get feedback early in terms of user experience and errors,” says Ben. When issues do arise, they are fixing them much faster. According to Ben, having Bugsnag “is the difference between fixing bugs and not fixing them. It’s infinitely faster.” Improved Pre-production Testing and Smoother Releases Using Bugsnag has empowered the QA team to improve their processes and facilitate smoother releases. Running test flights have been significantly sped up, and when they do find errors, they are able to easily reproduce them using Bugsnag’s automatic breadcrumbs. “It is incredibly helpful for QA to be able to provide steps to reproduce because it means there’s a 90% chance it’ll get fixed. Without steps to reproduce, it’s more like a 5% chance because it requires so much work from the developer to dig into and find out why or how it’s happening," says Senna. “JavaScript errors in particular are so edge-casey and hard to reproduce, and we’ve really appreciated having breadcrumbs that actually lay out step by step what a user did to get into this weird state that caused an error.” -Senna Bala, QA Engineering Manager Eventbrite now uses custom filters to monitor releases which has made shipping new features a much smoother process. During a release, new code is only deployed to one server which lets them monitor and fix issues while they are isolated. Eventbrite configured a custom filter in Bugsnag to filter errors by server so they can focus on the release and remove other noise from their view. When a release goes out, the engineers use this filter and monitor incoming errors on the server. This has helped them improve their releases and prevent rollbacks. “We’ve been able to catch a few errors that we wouldn’t have found in our QA process otherwise and been able to resolve those quickly rather than waiting for a customer to report them after a release.” DOWNLOAD CUSTOMER STORY PDF Also published . here

Bugsnag's Diagnostics Tools Benefits Eventbrite

Coupled with the growth of 99designs’ marketplace was the growth of their engineering team and the number of projects they managed. However, each team within engineering had their own way of troubleshooting bugs which was making it very difficult to work cross-functionally and creating many inefficiencies in the process. CHALLENGE: All of 99designs’ engineering team now uses Bugsnag to troubleshoot errors in more than 25 projects, written in multiple coding languages. By doing so, they have been able to quickly sift through the noise and solely focus on errors that really matter. This has allowed them to save valuable time, improve product quality, and onboard new engineers much faster. RESULTS: 99designs’ engineering team needed to standardize their process for troubleshooting errors in order to more easily sift through the noise and fix errors in an efficient manner. 99designs is the world's largest graphic design marketplace, with more than 400,000 customers soliciting help on design projects from 1.4 million freelance designers. As the number of customers and freelancers grew, so did the engineering team and the number of projects they were working on. Each of 99designs’ 7 engineering teams use multiple coding languages and are responsible for at least one of the company’s 25 codebases. This is when it became apparent that standardizing how error troubleshooting was done throughout the engineering team would create significant efficiencies in the process. Before Bugsnag, each team had its own tools and process for addressing bugs. In addition, many of the error monitoring solutions available in the market were tailored to Ruby developers, but 99designs was mainly a PHP shop. They needed an error monitoring solution that would allow them to proactively see the effects of deployed code, in multiple languages. Sifting Through the Noise with Clear Error Prioritization Bug tracking can easily become very noisy, causing engineers to ignore errors due to notification fatigue. In fact, before adopting Bugsnag, John Barton, Head of Engineering at 99designs, mentioned “someone had to first notice a bug in the firehose of errors before it could get worked on.” Once the bug was noticed, the process to triage and fix the error was very time-consuming and manual. “Bugsnag helped us smartly and automatically categorize errors upfront, which significantly simplified our developers’ lives. And it worked perfectly for all of our coding languages,” states Barton. With Bugsnag, 99designs has really tightened the feedback loop. As soon as something goes wrong, the right engineer to investigate it gets notified with minimal handoffs. Two features have really stood out for the 99designs engineering team: the Slack integration and error spike detection. If an unusual increase in errors occurs, the pertinent engineering team receives an alert in Slack. “Bugsnag helped us smartly and automatically categorize errors upfront, which significantly simplified our developers’ lives. And it worked perfectly for all of our coding languages.” - John Barton, Head of Engineering Higher Quality Code through Centralized Error Management The primary responsibility for Barton and his team is to keep all systems up and operational. “The one thing that has really changed for us is quality and increased team productivity. By having all of the information in one place, we can fix bugs faster than our customers can notice them, and therefore provide them with a great, reliable experience.” - John Barton In addition, having one single platform to manage errors has allowed 99designs to onboard new developers much simpler. They have all of the information in one place, and can become productive much faster. DOWNLOAD CUSTOMER STORY PDF Also published . here

How Bugsnag Helped 99designs Standardize Debugging and Create Efficiencies

We’re excited to announce that Bugsnag now supports stability management and error monitoring for applications built in Flutter. What is Flutter? Flutter is a cross-platform app development framework created by Google and powered by the Dart language that is rapidly growing in popularity. One reason for its growth is that Flutter lets developers use one codebase to build, test, and deploy their apps across multiple platforms. With Flutter, teams can create a single app for deployment across Android, iOS, web, and desktop platforms. Add in the fact Flutter is open source, and you can begin to understand why Flutter adoption is accelerating and why Flutter has become a true rival to React Native in the world of cross-platform frameworks. Bugsnag is excited to extend its full feature offering and support, including its game-changing , to “Flutter-first” apps for seamless integration. Our support for Android and iOS apps created with Flutter allows Flutter developers to enjoy Bugsnag’s actionable insights and analytics, support for progressive delivery of feature rollouts, real-time observability, and enjoyable user experience. Features Dashboard Gain Real-time Observability and Actionable Insights into Stability Development teams are releasing new versions and features for their apps more frequently to engage and retain users. With Bugsnag, you can understand the stability of every release and see how rapidly users are adopting new releases. Our Features Dashboard shows you the health of features released through progressive delivery to a subset of your customers. Based on the health score and performance of these new features, you can decide whether to release to your entire audience or pull back to refine functionality and fix any bugs first. Real-time stability scores can be compared against your configured target stability and critical stability for your app. The two thresholds help you make data-driven decisions on whether to build new features or spend time bug fixing. In short, if your app scores below your critical stability target, development teams must focus on bug fixing. If your app places above target stability, your app is running smoothly, and your development team can dedicate their time to building new features. Additionally, the interactive timeline analysis helps you understand stability issues over time. You can pinpoint error spikes, investigate specific incidents, determine if a release has introduced new bugs, and more. Not All Bugs are Worth Fixing Understand which bugs are occurring more frequently and impacting the most users. You can view errors grouped by root cause and sorted by user impact so you can make data-driven decisions about which errors need to be addressed first. Prioritize Fixing the Bugs that Matter Not all bugs are created equal. Bugs impacting VIP users or revenue-generating customers will most likely be placed higher on the list of importance over minor errors. Developers can effortlessly choose the metadata required to collect for each error, like spending tiers, then segment errors affecting high-paying customers. Errors impacting business-critical app functions, such as the user sign-up or in-app purchase flows, are also important to address quickly to minimize further impact to your business’ bottom line. Using error segmentation in Bugsnag, you can see which errors are impacting a certain part of the codebase, such as the one supporting e-cart purchases, so you can prioritize fixing them. Customize Error Views and Alerts Using bookmarks, which are a set of saved error segmentation filters, error views can be configured in the Project Overview Dashboard for each team member working on building and maintaining your app. An error view includes a feed of errors and a trend graph to show how errors impact the stability of the segment. You can set up error views for VIP users or superfans, in-app purchase flows, and even ad networks. Gaining visibility into errors originating from ad SDKs can help you decide if you need to turn off an erratic SDK that is negatively impacting the in-app experience. You can use the same bookmarks for configuring error alerts, so that you are only notified of errors occurring in segments that matter to you. This way you can improve the signal-to-noise ratio and focus the team on addressing errors that will have the greatest impact on improving app stability and user experience. Get to the Root Cause of Errors Quickly with Comprehensive Diagnostics Reproducing and fixing errors is easier when you can understand exactly what caused the crash. See comprehensive diagnostic information for every error, including symbolicated stack traces, user interaction breadcrumbs, and device and user information. Flutter doesn’t allow runtime access to the application version number or internal codes, so we used existing build IDs that exist on each platform (the build ID generated by the linker on Android, and the Mach-O UUID of the Dart code on iOS). This allowed us to exactly match up Flutter binaries with their debug information, allowing even obfuscated application stack traces to be symbolicated in the Bugsnag Dashboard. Streamline Debugging Workflows with Powerful Integrations There are pre-built integrations with the tools your team already uses, like Slack, PagerDuty, and 2-way issue tracker integration with Jira, Pivotal, and more. Automation can streamline your debugging workflows and drive code ownership so you can quickly roll out fixes. By tightly integrating our Flutter library with our existing iOS and Android native libraries, we cover the entire Flutter stack, including any native plugins in your apps, Dart FFI calls, and even the Dart runtime itself. The tight integration also means breadcrumbs and metadata created by the native layers will be logged as part of Flutter-specific errors, and the other way around. Get Started with Bugsnag Bugsnag’s new error reporting library for Flutter initially supports Android and iOS applications. Simply create a new Flutter project and follow the quick start guide in our documentation to begin monitoring your application. If you’re new to Bugsnag, start a 14-day free trial or request a demo to see the capabilities of our stability management platform in action.

Explore Error Monitoring and Stability Management for Flutter Applications with Bugsnag

This blog is derived from the App Stability Series webinar, “Unlocking Bugsnag's Power Features,” a series focused on showcasing Bugsnag’s most powerful features that deliver an effective app stability experience. As digital transformation accelerates across verticals and consumers continue to adopt more applications into daily life, the engineering organizations behind these applications need to scale their teams, infrastructure and processes accordingly. Demand for new and improved functionality pushes for shorter development cycles and drives the adoption of progressive delivery practices. Traffic and data volumes continuously increase and apps integrate with more third-party services, increasing interdependency. All of this puts a strain on the ability to efficiently monitor app health and stability, as well as identify root causes of bugs. There is quite a bit of flexibility within Bugsnag that can sometimes go unnoticed by our users. Although Bugsnag's main functionality can be stood up in a matter of minutes by adding our SDK to your application, we do have a lot of features to address problems at scale and have collected some smart solutions from working with our power users. Some of these best practices are laid out below for your teams to leverage. Not All Bugs are Created Equal Some bugs prevent users from being able to complete critical functions or revenue-generating activity. Some crashes can quickly be isolated from users if they are known to be specific to a release version or a feature toggle. Other functional problems, like ANRs, app hangs and out of memory exceptions (OOMs) could be coming from outside of your code itself. Some of the visibility and monitoring challenges we often hear from engineering teams, of every size and across all verticals, are: : Taking the live stream of exceptions and honing in on specific situations, like crashes in specific critical paths & user bases, crashes related to live ops issues like third party outages, or A/B tests going wrong. Isolating incidents : Utilizing engineering resources to manually triage incoming errors or investigate issues that turn out not to be priorities. This includes errors coming from low-end devices, bot traffic and browser extensions. Sifting through noise : Additional complexity is introduced when features are shipped more frequently. Further manual work is introduced in trying to correlate errors and find causation across many app versions and active experiments or feature flags. Correlating errors with specific releases or feature toggles How Bugsnag can be Configured to Protect Revenue and Reduce Noise In order to provide a richer context for your errors, custom metadata may be added. This is incredibly helpful in tracking additional business or industry specific attributes and allowing for this information to be searched against within your errors. Custom metadata opens a range of possibilities, especially since bookmarks allow you to save searches in your team’s inbox, track trends and automate alerting or ticket creation to specific error segments. Some relevant metadata concepts Bugsnag users leverage today are listed below. Key Metadata Concepts: : From eCommerce apps with loyalty or membership programs to gaming apps where users accumulate a lifetime spend, logging the customer's loyalty status to your app is a crucial way to segment and track the experiences of your most important user bases. Customer Tier/ Type We recommend segmenting out errors in production where the user is of high value – this way custom notifications can be leveraged to notify your customer success organization if there are spikes in errors in this segment. This gives the team the ability to proactively respond to any highly valued users who run into significant issues with your application. : Understanding if an ANR, app hang or OOM error is coming from a performance issue in the application or from the user's device can be a very valuable distinction to reduce noise and properly prioritize. Some Bugsnag users maintain an internal mapping of device manufacturer or name to a classification (i.e., low, medium, high), and add this as metadata. Device tier If you monitor ANRs, OOMs or app hangs in your app, we recommend implementing a similar mapping and adding device tier metadata, so that all bookmarks tracking these errors can specifically exclude any exceptions coming from low-end devices. : By default, Bugsnag provides metadata in Android, iOS, React Native, Unity and Unreal that identifies if the app was launching during the time of the exception. The point at which your app is considered “launched” is configurable and can be either time-based or declared manually (see the "Identifying Crashes at Launch" section of our documentation). isLaunching We recommend creating a “Launch Crashes” bookmark where the parameter isLaunching = true, as this will allow you to track trends in launch crashes. I also recommend taking a look at a led by Ivan Diaz, which includes a live demo on detecting and remediating crash loops from within your app code. webinar : Network request information can be an important indicator when monitoring errors. Information like the last requested service, last request status and last response duration are powerful metadata to track. This can provide insights for gaming applications connecting with ad networks, or for general live ops issues, such as detecting spikes in errors potentially caused by payment or other third-party service outages. Third Party Requests In iOS/Android applications, we recommend leveraging a callback function to check the event’s breadcrumb data for any network requests, and attaching the most recent network request details as custom metadata. Network breadcrumbs must be enabled in order to implement this approach. With this metadata added, it's possible to filter for errors where the last request was to a specific service or ad network, or to segment errors where the last request status was not 200, in order to assist in identifying correlations. : Within web applications, bot traffic will likely be prevalent and might even trigger errors that end up in your Bugsnag inbox. Given that these events aren’t impacting a true user's experience and most bot traffic identifies itself in the agent string, some Bugsnag users check for bot traffic and add metadata to flag if a session is from a bot. This way, any exceptions linked to bot traffic can be excluded as part of your search parameters. Bot Traffic These concepts outline just some of the ways in which custom metadata allows you to track more precise segments of errors, and how to leverage them to both isolate visibility around revenue and ops situations, as well as to reduce noise. Focus in on Stability of Releases and Feature Flags One of our newest additions to Bugsnag is the Features dashboard, which provides actionable insights into stability of feature rollouts. One of the key functions within the Features dashboard is the Errors Introduced section, which highlights any errors that are exclusive to a specific feature flag or experiment. Our Releases dashboard also provides a similar Errors Introduced section, allowing developers to understand if there are errors unseen in any other version. The Features and Releases dashboards allow developers to quickly understand if a release version or feature needs to be rolled back to preserve stability, and if code within a feature or release is causing specific exceptions. Many Bugsnag users aren't aware that the search builder allows you to filter the inbox for errors exclusive to a certain release version or feature flag. We recommend creating a bookmark for errors introduced in the latest version and linking this to alerting, so that your team is notified of new errors brought on by your latest release. This can also be done for new features being rolled out to your user base. Our Releases dashboard typically becomes the command center for mobile teams and release managers in the days after their latest release, as this view provides the ability to monitor both stability and adoption by version number in real time. This dashboard can begin to hold quite a bit of data for web applications, that sometimes deploy hundreds of times per day. For web applications, we recommend that version is set , in order to plug in a more easily identifiable naming convention such as the Git SHA, or even a unique identifier based on the timestamp of the release. manually Some of our major eCommerce Bugsnag web users leverage this best practice to get stability by version as well as identify exclusive errors to specific versions. Callback Functions Let You Customize Error Data For most platforms and error types, valuable information can be accessed and changed via callback functions, which gives you access to the error data before the event is sent to Bugsnag. This helps teams do things like customize error grouping logic, add and change metadata or context based on breadcrumb properties, and even add additional information to tricky errors such as OOM errors in iOS. Information on callback functions for your platform can generally be found under the "Customizing error reports" section of our documentation. In addition to implementing many of the metadata ideas mentioned earlier within a callback, some powerful examples of leveraging callback functions are below: : Some Bugsnag users pull error information to determine the team responsible for an error. They are then able to add the responsible team’s name as custom metadata to simplify filtering errors by relevant squad in the dashboard. This logic can range from checking characteristics of the stackframe URL in web projects to pulling the module out of the path in iOS/Android. Determine responsible team : We've worked with iOS teams on pulling the last navigated-to page or view in a callback, in order to add more context on where in the app users are experiencing OOM errors. Bugsnag provides crucial information for OOM exceptions like breadcrumbs and metadata, and this can be leveraged to display the context of the OOM, as well as to group errors more precisely, so that you can track trends in OOMs in views or modules individually. In the example below, the callback function checks for relevant information in the breadcrumbs and uses this to change the OOM’s context and grouping hash. Setting Context and Custom Grouping Other Configuration Best Practices We've shared a lot of valuable examples of how to set up and customize Bugsnag to gain additional insight. Some configuration best practices we generally recommend to our users are below that can be simple to implement yet yield powerful results. By default, Bugsnag stores up to 50 breadcrumbs for each error, meaning that any additional user actions, device changes or network requests that are collected may start to drop off after the limit. Within the configuration, most platforms offer the option to adjust this to a true maximum of 100. If you are running into this limit in the dashboard, we recommend adjusting this maximum as needed in your code. Max Breadcrumb limit: For web applications, another important way to reduce noise is by configuring allowed domains. Bugsnag enables you to add your domain to a list of allowed domains in our settings, so you can automatically ignore any JavaScript errors that happen on other domains. This way, your dashboard can focus solely on the errors you know are coming from your own code and exclude any browser extensions or debugging scripts. We recommend setting this for web customers, and more details can be found in our Allowed Domains: documentation. An app hang (iOS) occurs when an instance of the main thread fails to respond in some amount of time - this can occur when performing CPU intensive work or performing blocking I/O on the main thread. If your app hangs for 10 seconds or longer, it may be terminated by the system watchdog, which is considered a fatal app hang. If your iOS team would like to also report non-fatal app hangs to Bugsnag as well, we recommend setting in the configuration to a value such as 5000ms. This allows you to gain visibility into performance issues that are not necessarily causing fatal crashes. Setting Max Milliseconds Parameter for App Hangs: appHangThresholdMillis

Unlocking Bugsnag's Power Features: Gain Precision and Reduce Noise

This blog is derived from the webinar, “Accelerate Releases Through Code Ownership with Collaborator and Bugsnag”, focused on establishing a culture of code ownership and its benefits through the lens of the SmartBear tools Collaborator and Bugsnag. Taking a line from the SmartBear 2021 Annual State of Software Quality Report: "Quality is top of the mind for every individual and every team. Every developer has felt the pain of software releases that did not go well leading to customer calls and late nights. Quality software remains the insurance policy that continues to pay out." Engineering teams must constantly catch and remediate defects in order to ensure stable, high-quality applications. Testing and monitoring methods are typically applied throughout the entire software development lifecycle (SDLC) - from initial development, through testing and into production. With each added stage in the process, the relative cost of the issue increases. By the time an issue proceeds undetected into production, the reputation of the brand is on the line. One effective strategy to streamline bug identification and resolution through the SDLC is to leverage the practice of code ownership. In this blog we discuss , and how they drive a sense of clear responsibility, a factor proven to correlate with overall quality and efficiency in resolving issues. General code ownership principles by providing tools to help squads or code owners make decisions best suited to their parts of an application. How Bugsnag and Collaborator natively support and enhance this approach What Is Code Ownership? Code ownership is the idea that individual developers or teams are responsible for the features they create and deploy. For example, suppose that an ecommerce application has two teams responsible for user conversion and ecommerce. If there’s an error in the shopping cart, the ecommerce team owns the code and would be responsible for a fix. [source codeownership blog] We see many teams adopting what is referred to as code stewardship, or weak code ownership, where teams of engineers take general responsibility over building, testing and maintaining certain parts of the application. Benefits of Weak Code Ownership: : “The proportion of reviewers without expertise shares a strong, increasing relationship with the likelihood of having post-release defects.” [Code Ownership and Review Study]. Naturally, developers familiar with a certain part of an application should be responsible for other processes around it, such as reviewing code changes. Developers who have contributed to a module or function may have a deeper understanding of specific dependencies, data requirements or other tricky circumstances that need to be met when new code is added, and can catch more issues or incorrect assumptions if they have navigated this themselves. Minimizing Defects : By allocating code review and error monitoring responsibilities to a module’s owners, these codeowners can review code changes more efficiently as they are often already up to speed on their module’s functionality and context. Efficiency A culture of ownership encourages developers to take initiative as the subject matter expert of their code and actively participate in the relevant technical decisions. Granting teams the ability to monitor their own parts of the code, triage, prioritize and resolve their own issues, and review code changes with their own requirements brings the flexibility to tailor decisions around the functionality they understand. This fosters a healthier development environment. Culture: One example is tying error budgets to individual squads rather than defining this on the organization level. By doing so, teams can define their own error budgets and goals for their modules, which may bring more precision into those estimates on a company level. Challenges Below are some challenges we hear from teams implementing code ownership principles around their existing structures: How do we make sure teams get alerted of stability issues in the parts of the code they own? How do we align teams around which bugs to focus on? How do we make sure nothing slips through the cracks if there are gaps between what each team owns, or if things come through that no one team is specifically responsible for? How can we make this work within our broader ecosystem of tools, like JIRA, to minimize duplicating effort keeping things organized between all these data sources? How Do Collaborator and Bugsnag Fit in? helps development teams identify stability issues in every release and provides actionable insights to prioritize and fix those with the greatest impact. Bugsnag is an all-encompassing term for our many integrations with tools like Slack, JIRA and PagerDuty, as well as the intelligent logic layered on top to trigger and route alerts to the right people at the right times. Bugsnag's Alerting and Workflow Engine Bugsnag can be configured to alert the team who built the module or the integration when there are spikes in the errors coming from that code. The alert triggers can be tuned per module to ensure they are meaningful and align with that module’s behavior. For example, if one team is responsible for an app’s integrations with third party services, they may want to utilize spike detection to get alerted of potential outages. Another team might want alerts for every new error if they are responsible for rolling out a new feature. Teams should aim to minimize alert fatigue by adjusting alerting processes to follow code ownership boundaries. This helps to avoid high volumes of alerts firing off to one channel, where it is unclear who is responsible for what. : Engineering teams typically have pre-existing workflows built into their toolsets to support their squads, such as JIRA boards. Our integrations allow you to keep in sync with issue trackers and notification platforms in order to minimize cross management. Issue tracker integrations Our platform incorporates - teams can build a triaging process and know at any given time what the plan is for each error, so nothing gets lost in a high volume of data even when there may be gaps in coverage of errors. state tracking : A great example of an engineering organization that leveraged Bugsnag’s features to transform the way they triage and resolve issues around a code ownership model is found here: Customer story https://www.bugsnag.com/customers/gusto adds a level of accountability with clear, documented review processes and cross-functional alignment to catch errors early in your SDLC. Collaborator : Designed to fit into the same workflows as tools like GitHub and JIRA, Collaborator makes code review simpler, puts processes in place to give developers ownership of their code and facilitates bringing in peers in for additional approval of code shipped to production. Integrations with tools : Regardless of integration, a team’s workflow for review is the same for code artifacts as it is for documentation review, as it is for Simulink model review. Enforce process with a uniform workflow : For most integrations, Collaborator provides a gating mechanism to ensure artifact review before any release is approved, further shifting defect discovery earlier and enabling the release of the highest quality code possible. Provides review enforcement : 82% of teams satisfied with their code review process have specific guidelines on how they should be performed. [source] To create clear guidelines that ensure everyone on your team understands expectations, Collaborator lets you build custom checklists in review templates so participants with different roles and responsibilities can easily see what’s expected of them on each project. Custom rules to be set up per team Shift Left in the SDLC The vast majority of defects are typically introduced in the coding/development phase of the SDLC, but are mostly undetected until later phases, such as pre-production testing (unit tests, functional tests and system tests) and production. As seen below, an increasing number of bugs are typically found throughout the testing phases into release. The diagram highlights that the cost to repair a bug in a staging or production release is exponentially higher than a bug found during coding or early testing phases. This is in part because mean time to resolution is generally increased in later stages, and revenue or brand reputation can also take a hit when a bug is presented to your user base. Given there is a direct relationship between the number of code reviewers and the quality of the code post-review, the goal becomes shifting error identification and resolution earlier towards the coding phase through more robust peer reviews, supported by a tool like Collaborator. This in turn shifts the “percentage defects found” curve to the left, and lowers the cost associated with remediating those repairs, from developer’s time, user experience and brand loyalty perspectives. An ROI tool can be found on the Collaborator page, where you can drop in some basic figures for cost of developers, and quickly understand the advantages that early code review gives you as a return on investment. https://smartbear.com/product/collaborator/roi-calculator/ How Collaborator and Bugsnag Close the Loop Collaborator and Bugsnag in tandem allow teams to minimize the errors released into production with more thorough code reviews, while also providing robust monitoring and alert routing for those errors that do ultimately make it to your end users. We can see an ideal workflow below, illustrating the following: Customizable review and approval workflow completed in Collaborator by module owners to ensure code changes meet criteria. Approval of PR results in automatic merging of repositories, effectively applying the new changes to the codebase and moving changes forward for release. Once the newest release is in production, Bugsnag will begin to process events in real time from users that have adopted the new version. The Release dashboard will pick up the new version and monitor its live stability (crash free session and user rates). As new exceptions occur on user’s devices, Bugsnag will leverage information about where in the code the exception occurred and alert the right team to new errors or spikes in known errors in their modules, via our integrations. Once receiving an alert, developers leverage the information in the Bugsnag dashboard to triage, diagnose and prioritize the error. When the bug is ultimately addressed and fixed by the squad, this will result in some commits and a PR into GitHub, which will then kick off a new squad-specific review process via Collaborator to review and release the fix. To view live demonstrations of this feedback loop in the context of both tools, take a look at our full Webinar . here Additional Resources Bugsnag Code ownership Blog SmartBear Annual Report Code Ownership and Review Study

Use Collaborator and Bugsnag to Set Up a Code Ownership Loop

CHALLENGE Doximity sets out to improve application stability for its Android application as medical professionals rely on its services to communicate remotely. RESULTS The Android team improves app stability by aligning teams, streamlining workflow, and achieving 99.99% stability with Bugnsnag. About Doximity : Healthcare Industry : Android, iOS, Web App & Platforms : 650 Employees San Francisco, CA Headquarters: Doximity Delivers Remote Capabilities to Medical Professionals Doximity is the leading digital platform for medical professionals. Recognizing that clinicians are mobile by nature, Doximity delivers a suite of tools that enable verified members to perform their jobs on-the-go or while working remotely. The company’s network members include doctors, nurses, nurse practitioners, physician assistants, and pharmacists. Doximity and its Android mobile application serve an important need as medical professionals have turned to the multifaceted app for activities such as telemedicine, patient referral facilitation, and targeted medical news. “Just like everyone else these days, doctors are starting to work from home and need a way to contact their patients,” states Matt Rea, Android Engineering Manager at Doximity. “Any increase in usage can triple or quadruple any issues you might have in the app, so crashes and infrastructure errors can’t be taken lightly.” Focus on Stability Drives Visibility and Strong User Experiences In late 2019, the Android team implemented Bugsnag, which Matt describes as fortuitous. “Going into 2020, we had the goal to work on improving stability,” Matt explains. “Once I started looking into Bugsnag, I realized how full-featured it was. Luckily, we implemented Bugsnag, so that was perfect timing for us.” Another reason the Android team decided to implement Bugsnag was to benefit from its widespread adoption by Doximity’s backend and web teams. Approximately 75 projects and applications were already using the error monitoring solution. “We wanted to have one place, specifically Bugsnag’s Stability Center page, where we could view application health for the entire system” -Matt Rea, Android Engineering Manager If a major issue or outage happens or a database goes down, we can see everything that spikes,” Matt states. “That kind of high-level view is invaluable.” Rounding out the decision was a recognition by the Android team that they needed more than crash-free scores to ensure strong user experiences. Now with measuring application stability, Doximity gains a more reflective and holistic view of their application health. As Matt explains, “Looking at crashes is only one piece of the picture. Obviously, you never want an app to crash, but you also don’t want an app to be available but not useful. Those are the kinds of things that, looking only at crash-free ratings, for example, you would miss.” Bugsnag Fosters Productivity and Team Alignment with Remote Work Matt acknowledges that it is paramount for managers to ensure that employees are feeling confident with their work.  Finding ways to reduce burnout around tasks like error detection became a priority. “Bugsnag made it much easier to track down bugs,” Matt states. “Instead of banging your head against the wall to figure out how an error occurred, the breadcrumbs that Bugsnag attaches to errors really help. We make good use of breadcrumbs.” The team also benefits from integrating Bugsnag with Slack to receive focused error alerts. As the Android lead, Matt also appreciates the metadata that Bugsnag provides. “Android is a pretty fragmented ecosystem, so a bug might occur only on Samsung or LG devices or certain OS versions, which can be pretty hard to track down from a normal QA bug reporting perspective,” Matt explains. “Bugsnag gives the engineer more of a starting point, more of a big picture around ‘how did this occur?,’ which definitely makes things easier.” To minimize the impact of errors on its user base, the Android team takes advantage of phased rollouts, supported by Bugsnag. With two week release cycles, Doximity sends out new releases to only 10% of its user base to ensure there are no spikes in errors or crashes. “Tracking releases is one of my primary responsibilities—to make sure releases go out on time and are stable—so the Releases dashboard is one of my favorite features in Bugsnag.” -Matt Rea, Android Engineering Manager “We generally have several versions in production, so I can see the past five releases, what the adoption is on each release, and what the stability is for each release,” Matt states. Android Team Achieves Stability Score Target of 99.99% and Sets New Stability Goals for the Future After implementing Bugsnag, the Android team focused initially on resolving outstanding crashes to improve the overall stability of the app. “Thanks to Bugsnag, we were able to get on top of a few big crashes right away,” Matt explains. The team adopted Bugsnag’s stability targets in order to establish goals and achieve strong stability for users. “While 99.99% seemed pretty lofty and difficult to achieve, we got there over the course of 2019 and into 2020. I think it’s a pretty good goal to try to hit that 99.99% with each release.” -Matt Rea, Android Engineering Manager Today, the Android team benefits from streamlined workflows and a quick understanding of the source for any new errors. Next, they are starting to (application not responding) and native crashes for features such as video calling that use native libraries. Matt also plans to broaden his use of Bugsnag’s user stability score. “So far, I’ve been mainly focused on the session score, although I’ve been keeping an eye on the user stability score as well. I would like to start leveraging that in the future.” look into Android ANRs Download Customer Story PDF

Domixity Reaches 99.99% Stability on Android App with Bugsnag

Intent: Square wanted to provide a stronger error monitoring solution for its Point of Sales application and achieve a single source of truth for errors and crashes across its native applications. Result: By rolling out Bugsnag onto iOS, Square accesses all mobile stability management and error monitoring in one location, paving the way to introduce Bugsnag for all its future apps. Square Makes Merchant Services and Digital Payments Easy When Square, Inc. was founded in 2009, its objective was to provide an easier way for small business owners to accept credit cards from customers. Today, Square empowers companies of all sizes with a wide range of products and services for payments, loans, customer and employee management, and point of sale (POS) across multiple industries, including retail, food and beverage, and professional services. Over the years, Square has relied on various error monitoring solutions and used different tools for its Android and iOS applications. “We want to have a single source of truth for crashes across our apps, and we want to be able to apply multiple filters to triage an issue,” explains Anil Umarji, Engineering Manager, Quality, who oversees the Release Operations (RelOps) and Quality (QA) teams. Consolidating Error Monitoring for Native Apps is a Top Priority Seven years ago, Square’s Android team migrated to Bugsnag from previously using Crashlytics. Pierre-Yves (PY) Ricau, Staff Engineer, focuses on crashes and performance for Point of Sales (POS) and remembers why Square moved to Bugsnag for its Android error monitoring. “Crashlytics was originally built for iOS. When the company was acquired by Twitter, the team then built an Android solution that wasn’t as customizable and stable as we would have liked,” explains PY. “What Bugsnag brings to the table is extensive around things like custom indexing, filtering, and searching. It’s a game changer.”— PY Ricau, Staff Engineer In 2014, when Square adopted Bugsnag for Android, PY noticed an immediate improvement: “With Bugsnag, we have the source of a crash or error right there, which is something we didn’t have with Crashlytics. What Bugsnag brings to the table is extensive around things like custom indexing, filtering, and searching. It’s a game changer.” Today, Bugsnag is rolled out to Square’s full stack, including web and backend. The iOS team is finishing up its migration to Bugsnag from previously using Crashlytics, which is now Firebase. “We didn’t have a tool from the iOS perspective where we could apply multiple filters to triage an issue,” states Anil. “From a RelOps and QA perspective, we want to get the best of what’s on Android on iOS. After all, we have unique filters on Bugsnag, and the UI is pretty intuitive. We want that same functionality for iOS, too.” Bugsnag Error Details and Custom Filters Enable Experimentation, Investigation, and Timely Releases Because Square uses a lot of shared code across systems, it’s critical that any new features don’t break or affect other features. The move to Bugsnag for the iOS team will simplify QA and RelOps work by providing a single place to look for errors. “Point of sale is an intersection of all the other verticals at Square. Having POS for both Android and iOS on Bugsnag will help other teams know where the crashes and out-of-memory issues are,” explains Anil. “That’s the biggest advantage I can see from my team’s perspective.” The RelOps team currently uses Bugsnag for Android throughout its bi-weekly release development cycle and relies on Bugsnag to quickly address bugs that affect stability. “The Bugsnag dashboard is our go-to page every day to see what’s happening. There are two things we look at: production and our continuous testing,” states Anil. “We use phased rollouts for both Android and iOS, and we use Bugsnag to look at stack traces to see if a similar crash happened in the past and determine if it’s a new crash.” “The Bugsnag dashboard is our go-to page every day to see what’s happening.”— Anil Umarji, Engineering Manager, Quality “The investigation piece is where Bugsnag shines,” states PY. “We can add metadata to breadcrumbs, which helps us understand the steps that led to a crash. And, when you define custom filters, you can then define a list of crashes for a specific set of conditions.” All new features in Square are also behind a Bugsnag feature flag for easy identification. “From a feature stability perspective, tags help us to know if something broke with the new feature or if it’s something we’ve already found and tagged as one of our critical features,” explains Anil. “We also use custom tags in Bugsnag to make sure there are no regressions.” There’s one Bugsnag feature in particular that PY believes is a hidden gem. “When I don’t know exactly which crash I’m looking for, Bugsnag’s Timeline view is like gold. It provides visual clues about error rate changes and lets us filter, which is especially helpful for determining if an error is server-related. That type of information is invaluable.” “When I don’t know exactly which crash I’m looking for, Bugsnag’s Timeline view is like gold.”— PY Ricau, Staff Engineer Square Banks on Bugsnag to Encourage Product Ownership With teams using one solution for error monitoring and stability, Anil believes Bugsnag will further encourage ownership over the different parts of the applications. “Bugsnag has been a super helpful tool for us from an Android standpoint, and I hope very soon to replicate that with iOS as well,” states Anil. Looking forward, Square knows its partnership with Bugsnag will help achieve stability across its native applications and full stack. As Anil states, “One thing I really like about Bugsnag is the flexibility to develop what’s on top of what’s already there and the ability to ask for new feature sets from the Bugsnag team.” “Bugsnag is definitely made for the professional,” PY states. “And Bugsnag is still the best out there.” Previously published here. Intent: Intent: Square wanted to provide a stronger error monitoring solution for its Point of Sales application and achieve a single source of truth for errors and crashes across its native applications. Result: Result: By rolling out Bugsnag onto iOS, Square accesses all mobile stability management and error monitoring in one location, paving the way to introduce Bugsnag for all its future apps. Square Makes Merchant Services and Digital Payments Easy When Square, Inc. was founded in 2009, its objective was to provide an easier way for small business owners to accept credit cards from customers. Today, Square empowers companies of all sizes with a wide range of products and services for payments, loans, customer and employee management, and point of sale (POS) across multiple industries, including retail, food and beverage, and professional services. Over the years, Square has relied on various error monitoring solutions and used different tools for its Android and iOS applications. “We want to have a single source of truth for crashes across our apps, and we want to be able to apply multiple filters to triage an issue,” explains Anil Umarji, Engineering Manager, Quality, who oversees the Release Operations (RelOps) and Quality (QA) teams. Consolidating Error Monitoring for Native Apps is a Top Priority Consolidating Error Monitoring for Native Apps is a Top Priority Seven years ago, Square’s Android team migrated to Bugsnag from previously using Crashlytics. Pierre-Yves (PY) Ricau, Staff Engineer, focuses on crashes and performance for Point of Sales (POS) and remembers why Square moved to Bugsnag for its Android error monitoring. “Crashlytics was originally built for iOS. When the company was acquired by Twitter, the team then built an Android solution that wasn’t as customizable and stable as we would have liked,” explains PY. “What Bugsnag brings to the table is extensive around things like custom indexing, filtering, and searching. It’s a game changer.”— PY Ricau, Staff Engineer “What Bugsnag brings to the table is extensive around things like custom indexing, filtering, and searching. It’s a game changer.” — PY Ricau, Staff Engineer In 2014, when Square adopted Bugsnag for Android, PY noticed an immediate improvement: “With Bugsnag, we have the source of a crash or error right there, which is something we didn’t have with Crashlytics. What Bugsnag brings to the table is extensive around things like custom indexing, filtering, and searching. It’s a game changer.” Today, Bugsnag is rolled out to Square’s full stack, including web and backend. The iOS team is finishing up its migration to Bugsnag from previously using Crashlytics, which is now Firebase. “We didn’t have a tool from the iOS perspective where we could apply multiple filters to triage an issue,” states Anil. “From a RelOps and QA perspective, we want to get the best of what’s on Android on iOS. After all, we have unique filters on Bugsnag, and the UI is pretty intuitive. We want that same functionality for iOS, too.” Bugsnag Error Details and Custom Filters Enable Experimentation, Investigation, and Timely Releases Bugsnag Error Details and Custom Filters Enable Experimentation, Investigation, and Timely Releases Because Square uses a lot of shared code across systems, it’s critical that any new features don’t break or affect other features. The move to Bugsnag for the iOS team will simplify QA and RelOps work by providing a single place to look for errors. “Point of sale is an intersection of all the other verticals at Square. Having POS for both Android and iOS on Bugsnag will help other teams know where the crashes and out-of-memory issues are,” explains Anil. “That’s the biggest advantage I can see from my team’s perspective.” The RelOps team currently uses Bugsnag for Android throughout its bi-weekly release development cycle and relies on Bugsnag to quickly address bugs that affect stability. “The Bugsnag dashboard is our go-to page every day to see what’s happening. There are two things we look at: production and our continuous testing,” states Anil. “We use phased rollouts for both Android and iOS, and we use Bugsnag to look at stack traces to see if a similar crash happened in the past and determine if it’s a new crash.” “The Bugsnag dashboard is our go-to page every day to see what’s happening.”— Anil Umarji, Engineering Manager, Quality “The Bugsnag dashboard is our go-to page every day to see what’s happening.” — Anil Umarji, Engineering Manager, Quality “The investigation piece is where Bugsnag shines,” states PY. “We can add metadata to breadcrumbs, which helps us understand the steps that led to a crash. And, when you define custom filters, you can then define a list of crashes for a specific set of conditions.” All new features in Square are also behind a Bugsnag feature flag for easy identification. “From a feature stability perspective, tags help us to know if something broke with the new feature or if it’s something we’ve already found and tagged as one of our critical features,” explains Anil. “We also use custom tags in Bugsnag to make sure there are no regressions.” There’s one Bugsnag feature in particular that PY believes is a hidden gem. “When I don’t know exactly which crash I’m looking for, Bugsnag’s Timeline view is like gold. It provides visual clues about error rate changes and lets us filter, which is especially helpful for determining if an error is server-related. That type of information is invaluable.” “When I don’t know exactly which crash I’m looking for, Bugsnag’s Timeline view is like gold.”— PY Ricau, Staff Engineer “When I don’t know exactly which crash I’m looking for, Bugsnag’s Timeline view is like gold.” — PY Ricau, Staff Engineer Square Banks on Bugsnag to Encourage Product Ownership With teams using one solution for error monitoring and stability, Anil believes Bugsnag will further encourage ownership over the different parts of the applications. “Bugsnag has been a super helpful tool for us from an Android standpoint, and I hope very soon to replicate that with iOS as well,” states Anil. Looking forward, Square knows its partnership with Bugsnag will help achieve stability across its native applications and full stack. As Anil states, “One thing I really like about Bugsnag is the flexibility to develop what’s on top of what’s already there and the ability to ask for new feature sets from the Bugsnag team.” “Bugsnag is definitely made for the professional,” PY states. “And Bugsnag is still the best out there.” Previously published here. here.

Square Case Study: Bugsnag Struck Gold When Building the Timeline View

Dropbox values product health and developer productivity. Since its first product release in September 2008, Dropbox has focused on delivering a modern workspace where users can store, access, and collaborate on content. Today, Dropbox’s global collaboration service provides a wide range of business and personal offerings around cloud storage, document collaboration, and file synchronization that are accessible on web, desktop, and Android and iOS mobile applications. “Product health is one of our highest focuses,” states Angella Derington, Dropbox Mobile Staff Engineer. “One of the things we want to achieve for all of our mobile apps is to hit the three-nines on user availability. To do that, we need tools that any engineer can utilize to troubleshoot where crashes come from and identify what’s happening in each release.” Moving From Homegrown to Crashlytics to Bugsnag Years ago, Dropbox built a homegrown crash reporting system. However, staffing and resourcing dropped off over time, which led to a stagnant system that did not provide the features required to monitor application health. Approximately two years ago, the observability team, which owned all tooling to observe behaviors on client applications, recognized the need to adopt a new error monitoring solution that would evolve faster and enable Dropbox to benefit from the expertise of a third-party provider. Evaluation of external crash reporting solutions began, with the objective to find a solution that could be implemented company-wide. To bridge this interim period, the mobile team decided to try a free solution. “We moved to Crashlytics for about a year, which was an improvement from our homegrown solution but lacked a lot of things, especially breadcrumbs and query tools,” states Angella. “The mobile engineers were easy to convince because there’s so much functionality with Bugsnag, and it’s easy.” ‍ — Angella Derington, Mobile Staff Engineer When Dropbox selected Bugsnag as its stability monitoring solution, Angella’s team became the first internal customer. “The mobile engineers were easy to convince because there’s so much functionality with Bugsnag, and it’s easy,” explains Angella. “It was a very smooth transition, and I think the full migration took us only about six weeks. We’d already abstracted our crash reporting library, so it was pretty straightforward to plug in Bugsnag.” Bugsnag provides full visibility during error investigation and experiments with breadcrumbs, automatic grouping, and custom filtering. Today, Bugsnag enables the Dropbox mobile team to monitor stability by release and prioritize and fix errors with speed, precision, and ease. Breadcrumbs is one of the critical Bugsnag features that the team relies upon as a best practice for debugging why a crash happened and for resolving customer complaints. “When we moved to Bugsnag — especially with its breadcrumbs — engineers were suddenly saying, ‘I can look at a crash and know how to fix it!’” — Angella Derington, Mobile Staff Engineer “Bugsnag removes uncertainty and anxiety around the time it takes to troubleshoot a crash and any concerns about reproducibility. Having information that pinpoints where to start looking in the code is groundbreaking for engineers,” states Angella. In addition to breadcrumbs, the mobile team benefits from indexing of custom events, which is particularly useful with its weekly beta releases. “I had never experienced or seen indexing of custom events in a solution before,” states Angella. “We do a lot of A/B testing and feature gates, and it’s extremely helpful to be able to index so you can create queries and bookmarks around them.” Historically, identifying the impact on a class of crashes proved hard to accomplish. “We’ve used Bugsnag a lot to identify impact and be able to fix classes of crashes a lot faster than we would have otherwise,” explains Angella. Out-of-the-box ANR detection and workflow integrations make debugging precise and actionable, while bookmarking and custom alerts help teams stay focused. The team also uses bookmarks on queries: “While Bugsnag does a pretty good job of identifying similar crashes, sometimes exceptions are chained. It’s helped a lot to be able to set up a bookmark that’s looking specifically for the exception message and be able to find all of those errors.” The Android team especially appreciates Bugsnag’s ability to handle Application Not Responding (ANR) errors. “I love that ANRs are in the tool. On previous teams, we’d forget about ANRs until customer complaints start coming in because we weren’t monitoring them in our tool,” states Angella. “Bugsnag is the first crash reporting tool where it’s actually being sucked in from Google Play, which is perfect.” Dropbox uses Bugsnag’s integrations with Jira, Slack, and PagerDuty to automate tickets and provide targeted, customized alerting. “In the past, we’ve turned off alerting because this fragmentation amounts to so much noise that no one pays attention to,” states Angella. “The ability to be specific about what you want to be alerted about from your crash reporting tool is very helpful.” With a passion to deliver high quality apps, Dropbox expands Bugsnag usage, allocating the time-saved ROI towards building new features Dropbox’s mobile teams use breadcrumbs for application health, and this best practice is spreading to the rest of the organization. “With newer Dropbox apps like Passwords, it’s a simpler task to build out breadcrumbs and handled exceptions in our code base,” states Angella. “The original Dropbox app, which has evolved from the very beginning, is around half a million lines of code right now and at varying stages of age, so it will take a little longer before it’s as end-to-end as apps like Passwords.” Today, the teams working on this desktop client application are putting in the work to add breadcrumbs throughout the large code base. This critical step will create consistency with logging and enable other engineering teams to fully benefit from Bugsnag in the same ways that the mobile teams are today. “It’s a passion of mine to deliver high-quality applications, especially ones that I work on. Of course, engineers don’t love fixing crashes; they like building new code. Minimizing that time with Bugsnag is magical.” — Angella Derington, Mobile Staff Engineer Previously published here. Dropbox’s mobile team set the goal to achieve three nines of user availability by the end of 2021, which would bring it in line with the team’s session stability score. With Bugsnag, mobile engineers have the stability management features required to monitor release stability and address errors with speed in order to improve the user stability score.

A Little Dropbox, Bugsnag, and a Lot of Visibility During Error Investigation 

Mercado Libre faced exponential user growth for its mobile applications when the global pandemic hit, putting pressure on the mobile teams to deliver stable, crash-free apps. Challenge: By upgrading to Bugsnag’s Enterprise plan and scaling usage across mobile teams, Mercado Libre handled a significant increase in mobile purchases during COVID-19 pandemic while achieving a 99.93% stability score to provide a better user experience for all their customers. Results: Mercado Libre embraces surge in mobile app usage during the pandemic Mercado Libre is on a mission to democratize commerce, payments, and money in Latin America. Operating in 18 countries with two main business units — eCommerce and FinTech, the company is best known for its online marketplace and its payment platform for online sales as well as in-store payments. Today, it is the largest online retailer in Latin America. While mobile app usage has increased steadily over the last three years, Mercado Libre experienced a sharp jump in app downloads and usage at the onset of the global pandemic. “Our market mobile share grew from about 20% to 70% over three years. We suddenly had more traffic, more users, and more developers, so we needed a full diagnostics tool that we could trust to monitor the stability of our applications.” — Juan Ucciani, Senior Product Manager Shift in consumer behavior shines spotlight on mobile app stability Originally, the mobile engineering teams at Mercado Libre used a common logging solution for error monitoring. However, it also lacked the search and filtering capabilities needed to find and fix errors. In order to deliver a world-class experience to their users, Mercado Libre made the switch to , and started gaining value from automatic error grouping and the ability to prioritize errors with breadcrumbs, search, and filtering. When Bugsnag introduced stability management, Mercado Libre was impressed by the diagnostics capabilities, which allowed its mobile teams to monitor all applications and deliver stable application experiences. Bugsnag Mercado Libre faced a new challenge when the global pandemic hit in 2020. Suddenly, consumers were downloading and using mobile apps in droves. This considerable shift to online shopping was expected to happen in three-to-five year’s time, but in reality seemed to have arrived within six-to-eight months. Bugsnag enables rapid growth with stability scores and diagnostics Mercado Libre benefited from Bugsnag’s full-stack capabilities and the ease of scaling usage over time. As Juan explains, “Bugsnag is really important to us for the whole ecosystem, not just the IT team. We needed full access to everything that Bugsnag could give us.” Today, all mobile projects use Bugsnag, and each mobile team views its own stability score, which rolls up into a global stability score. “We have about 60 teams adding code to our two main applications for release. Error tracking is really important because any big crash, or any increase in our crash rate, will stop that release, and we have a lot of features in every release,” Juan states. The engineering and product teams use Bugsnag to communicate and share a common language around monitoring, as well as to evaluate adherence to SLAs by using error rates. “The technical team and product team meet up and figure out how they did each quarter. It’s not just about rolling out products; it’s also about stability, errors, and crash rates, because in the end, all these are key to a great user experience,” Juan states. In addition, Bugsnag enables the teams to prioritize bug fixing and is crucial for diagnostics, especially the search and filtering capabilities. “Some cases, you need to go deeper in filtering in order to understand where an issue belongs,” Juan states. “Bugsnag is useful when you need to dig in and see where an error comes from in order to replicate the bug.” Mercado Libre also benefits from Bugsnag’s alerts and integrations. As Nahuel Barrios, Engineering Manager for the Mobile Architecture Team, states, “We used to receive alerts by email, but now we have the Slack channel integration. Some teams use it with specific filters to separate errors by team, allowing them to focus on their specific areas of code and react to error notifications as quickly as possible. We also use to pipe data into our own dashboards.” webhooks Mercado Libre achieves higher stability score while matching consumer demand for smooth mobile shopping experiences In a period of rapid growth, the mobile teams have accelerated offerings while maintaining an impressively low crash rate, thanks to their focus on stability as a main KPI. “Before using Bugsnag, we considered a stability score lower than 99.70% to be critical. Today, the average stability score is 99.93%, and we’re continuously working to set that baseline higher.” — Nahuel Barrios, Engineering Manager As the end of 2020 approaches, Mercado Libre is embracing the peak holiday season. While this time of year is especially busy for eCommerce, with the pandemic, it has become even moreso. Gift shopping is now wholly reliant on eCommerce platforms as brick-n-mortar stores are currently unavailable. In a dynamic environment, Mercado Libre trusts Bugsnag for reliability and peace of mind Because Mercado Libre is a multinational company, country-specific requirements must also be managed within its apps. They must adapt to each country’s laws and regulations, and new features take time to roll out to every country. Thus, mobile teams must manage stability and errors across different versions of the same app. In addition, Mercado Libre must build new features to ensure the company is always compliant with local laws. A new country’s regulations on FinTech means that the engineering team must adapt quickly. Stability management is not only important for improving user experience, but also for making sure their app remains healthy through sudden changes. “We use Bugsnag because we know how to use it, and we trust it, which is most important. We can trust that what we see is what is happening.” — Nahuel Barrios, Engineering Manager

Mercado Libre Achieves 50% Growth in Mobile Market Share with a 99.93% Stability Score 

Let's learn about via these 51 free stories. They are ordered by most time reading created on HackerNoon. Visit the to find the most read stories about any technology. Bugs /Learn Repo It’s not a bug – it’s an undocumented feature. 1. How to Upload Source Maps to Sentry with Next.js Troubleshooting with source maps uploading to Sentry with Next.js 2. What You Should Have Asked Your Teachers About Underestimating Bullet Issues Bullet issues… Each IT project has tasks of this type. They are small, simple, but once you forget about them, something gets killed suddenly. 3. Android High Memory Pressure: How to Diagnose and Fix the Errors On lower-end devices things start to get messy if a running app is taking up more than its fair-share of memory. The result of this situation is memory pressure 4. The Noonification: Do Leaders Really Need Emotional Intelligence? (10/14/2022) 10/14/2022: Top 5 stories on the Hackernoon homepage! 5. Professional Debugging in Rails Debugging is as important as writing code, it can cause your program to crash or behave unexpectedly. Most of the time, debugging can be very stressful, especially when one doesn’t use the right tools to debug. 6. The 1990's Called, They Want Their Bug Reporting Process Back Software development has improved 100x since the internet was invented, but how people report bugs has not changed since the 1990s. 7. How HotelTonight Prioritizes Finding and Fixing Critical Bugs While Maintaining a 1% Error Budget The stability score in particular has made it possible for their team to measure their application’s stability & maintain their team’s error budget of 1% error. 8. Unlocking Bugsnag's Power Features: Gain Precision and Reduce Noise How to efficiently monitor app health and stability, as well as identify root causes of bugs 9. How to Achieve Effective and Efficient Bug Triage In this section, we're going to dig into several Bugsnag features that help to answer those questions and solve those problems. 10. Bugged: A Thrilling Tale of Tech Troubles and Triumph When a strange bug starts causing problems in her mobile app, a determined developer sets out to fix it at all costs. 11. The Art of Debugging How to debug your code 12. The Commonalities Between Locating Bugs and Crime Solving A year ago, I got an offer for the role of QA Manual Engineer at inDriver. But before that, I spent seven years investigating criminal cases. 13. 3 Web Design Factors to Ponder Before Starting an E-commerce Venture Developing a website for an e-commerce venture is a process that needs to be done with deft care. Starting a website is easy, but to maintain it is the real deal. That's why you need to start the process with all the precautions and preparation as anything can go wrong. Web design and development is very difficult and can look impossible to perfect, especially for the newcomers. 14. Follow These Tips If Your Android Apps Keep Crashing There are several factors to cause apps to crash on your Android smartphones. Sometimes one or several bugs are responsible for crashing the apps. 15. Debugging Simple Arrow Functions More Efficiently Let's say we have the function below. 16. Explore Error Monitoring and Stability Management for Flutter Applications with Bugsnag Explore Error Monitoring and Stability Management for Flutter Applications 17. Counting The Cost of Software Bugs According to a study from 2016, software failures cost the worldwide economy $1.7 trillion! 18. How to Debug Streams and Collections Java 8 streams improved code readability they also provide great debugging opportunities. There are amazing tools for inspecting collections & arrays. 19. Bug Bounties: Battling Zero Day Vulnerabilities In the midst of the bear market and regular hacks, it seems like barely a week goes by without a headline declaring ‘crypto chaos’ and the end of web3. 20. Most Software Bugs Are Not From Lack of Knowledge Software culture with respect to errors seems to be "if you just". Errors are blamed on lack of knowledge. To progress as an industry we need to change that. 21. Common Mistakes in Bug Reports and How to Fix Them Common mistakes in bug reports. 22. Let's Stop Calling them 'Bugs' - Software Quality is Our Responsibility The term Bug sounds like an excuse out of our scope infecting our systems. It is not. Software quality is under our control. It is our responsibility to deliver 23. Fine-tune Your Product In No Time Being experts in the IT industry, we at QAWERK know about the importance of testing and want to share this knowledge as we believe high-quality software is the key to success. 24. How to Fix Error CS0246: "Type or namespace not found" in .NET Core Diving into error CS0246 - type or namespace could not be found, what it means, why it happens, and how to solve it. 25. How Should You Estimate Bugs? Countless hours have been spent by teams all over the world debating over this. But really, should you? 26. Financial Damage Caused by Software Bugs The damage caused by software bugs is undermined. Here's a look at the issue of technical debt caused by bugs, with example cases. 27. One of These Fonts is Not Like the Other This Slogging thread by David and richard-kubina occurred in hackernoon's official #techsupport channel, and has been edited for readability. 28. The Ultimate Guide to Product Bugs:  Part 1 Most bugs arise from mistakes and errors made in either a program’s design or its source code, or in components and operating systems used by such programs. 29. Why is Code Ownership Important to Application Bugs Fixing? Why is Code Ownership Important to Application Bugs Fixing? 30. What if Malware isn’t Slowing Down Your Games? Most experienced gamers realize that many different kinds of malware can slow down their games. 31. What We've Learnt From 3000 Bug Reports When do people report bugs? You probably never asked yourself that question, which was one of the reasons we wanted to answer it. The second reason was that we had the right type of data available, since our tool helps teams report and fix bugs. Long story short, we decided to learn more about the way software development teams approach the bug reporting process. For that exercise we've taken a random sample of 3000 bug recordings uploaded to our database in the last 2 months. Here's what we found. 32. How Application Stability Management Affects Developer Productivity See how Application Stability Management (ASM) drives developer productivity and smooths the user experience. 33. The Ultimate Guide to Product Bugs [Part 3] This is Part 3 of a comprehensive guide to product bugs. This part of the guide focuses on product bug reports. It provides templates and examples that you can take and apply straight away. Then, through the reports, you’ll see various ways of presenting information so that you and your stakeholders can make good decisions about bugs. 34. "We Don't Expect Software to Work Any Longer": A Non-trivial Interview with Natallia Shauchenka To kick off this interview, can you tell us what companies you have worked for? 35. Mobile App Debugging: Localizing Defects and Making Bug Reports Mobile app debugging requires the creation of bug reporting. In this article, I'll describe how to localize mobile app defects and create mobile app bug reports 36. Y2K22: The Problem that Caused Millions of Emails Worldwide to go Undelivered The Y2K22 Bug is the consequence o very bad software design 37. Pro Tips For Crowdsourced Penetration Testing Bug bounties, crowd-sourced penetration tests are increasingly becoming popular. See the top six tips for participating in a bug bounty program. 38. Use Automation to Streamline Debugging in Multi-Team Apps Use Automation to Streamline Debugging in Multi-Team Apps 39. Removing Bugs in Git When you are working on a huge project, you may discover bugs in the code that prevent you from proceeding any further in your development. How to fix them? 40. Canaries to the Rescue: Catching Service Issues Before the End User In this post, you'll learn the concept of canaries, example code, best practices, and other considerations, including both maintenance and financial costs. 41. The Ultimate Guide to Product Bugs [Part 2] This is Part 2 of a comprehensive guide to product bugs. Part 1 explored what product bugs are, why they occur, where they come from, and why they do and don’t matter. Part 2 focuses on how to manage product bugs. 42. Top 10 Bugs Found in C++ Projects in 2020 Top 10 Bugs Found in C++ Projects.
Modulo division by one
delete instead of delete[]
Buffer overflow
Meaningless overflow protection 43. Debug User Complaints Better by Logging Errors in Support Requests Customer support requests can be ambiguous and frustrating. Here's how to create more visibility into problems affecting your users. 44. Top 10 C++ Open Source Project Bugs Found in 2019 Another year is drawing to an end, and it's a perfect time to make yourself a cup of coffee and reread the reviews of bugs collected across open-source projects over this year. This would take quite a while, of course, so we prepared this article to make it easier for you. Today we'll be recalling the most interesting dark spots that we came across in open-source C/C++ projects in 2019. 45. Spotlight on the Server-Side: A Guide to SSRF Vulnerabilities Server-side request forgery (SSRF) vulnerabilities can lead to total system compromise. Discover where they’re common, examples, and prevention tips. 46. Introduction to Git Bisect: Find Commits that Introduced a Bug The Git Bisect command uses a binary search algorithm to find which commit in your project’s history introduced a bug. 47. Fixing Code Errors in Amnesia: The Dark Descent Just before the release of the "Amnesia: Rebirth" game, the vendor "Fractional Games" opened the source code of the legendary "Amnesia: The Dark Descent" and its sequel "Amnesia: A Machine For Pigs". Why not use the static analysis tool to see what dreadful mistakes are hidden in the inside of these cult horror games? 48. Bugs from the 90's: The Code of Command and Conquer [Volume 2] The American company Electronic Arts Inc (EA) has opened the source code of the games Command & Conquer: Tiberian Dawn and Command & Conquer: Red Alert publicly available. Several dozen errors were detected in the source code using the PVS-Studio analyzer, so, please, welcome the continuation of found defects review. 49. What Are the Best Practices for Triaging Software Bugs If your app, or your game, or your web service isn't working perfectly for every interaction, then it's time to think about bug triaging. 50. Bugs From the 90's: The Code of the Command & Conquer Game The American company Electronic Arts Inc (EA) has made the source code of the games Command & Conquer: Tiberian Dawn and Command & Conquer: Red Alert publicly available. This code should help the game community to develop mods and maps, create custom units, and customize the gameplay logic. We all now have a unique opportunity to plunge into the history of development, which is very different from the modern one. 51. How to Develop a Bug Triage Process Efficiently You're going to need to find a way to incorporate bug triage practices into your overall engineering process. So let's talk about some ways to accomplish that. Thank you for checking out the 51 most read stories about Bugs on HackerNoon. to find the most read stories about any technology. Visit the /Learn Repo

51 Stories To Learn About Bugs

Customers have little tolerance for errors in web, mobile, and desktop applications. According to , 80% of enterprises say a slowdown to a mission-critical application would have a moderate to severe impact on overall business performance. As a result, it's critical for software development teams to have an error monitoring strategy in place. Riverbed Let’s look at error monitoring, why you might want to consider it, and the best practices with Bugsnag. Error monitoring solutions have become essential for software businesses, given rising customer expectations and growing competition. What is Error Monitoring? Error monitoring, also known as error tracking, tracks bugs and errors in applications to ensure that they work seamlessly at all times. In addition to discovering new bugs, error monitoring solutions help triage and fix them. The goal is to provide a consistent and error-free user experience while minimizing the time it takes to fix bugs. Error monitoring falls into two categories: – Front-end monitoring looks at software from the user’s perspective, catching errors in browsers or mobile devices. For example, test engineers might test a new feature in browser instances to ensure there aren’t any errors in the console. Front end – Back-end monitoring identifies errors occurring on servers or across the associated infrastructure. For instance, test engineers might monitor server logs for unhandled exceptions or monitor infrastructure to ensure sufficient memory. Back end can help simplify these strategies. Full-stack, end-to-end monitoring capabilities enable developers to quickly find and reproduce errors, separate critical errors from garbage errors, and generate a high-level analysis of application-wide errors to support DevOps teams’ deployment decisions. Error monitoring solutions 3 Core Benefits of Error Monitoring Error monitoring helps reduce the number of errors reaching production users, but that’s far from the only benefit of using error monitoring solutions. Effective error monitoring strategies also can improve a development team’s efficiency and reduce revenue loss. When combined, these benefits often translate to a strong return on investment. 1. Better Customer Experience Customer experience has become the defining metric for success, but many organizations fail to recognize the importance of error monitoring in improving the customer experience. While an effective test suite can catch major bugs before deployment, many bugs don’t appear until after the code reaches production users. Unfortunately, in today’s hyper-competitive world, many customers will move on to the next product rather than report any issues or bugs they experience. As a result, error monitoring is the only truly effective way to uncover and fix problems that unit and end-to-end tests miss – and, therefore, the only way to ensure the best user experience. 2. More Efficient Developers With reproducing the error and tracing problems from the front end to the back end, conventional bug tracking involves a lot of detective work. In particular, front-end errors can be tough to reproduce since they might be browser- or device-specific. And as a result, developers might waste a lot of time they could spend building features. Fortunately, error monitoring solutions can dramatically improve efficiency by tracing errors across the application stack, adding bug reports to issue trackers, and even communicating them to the right team members to fix. By automating these tasks, developers can minimize the time they spend fixing bugs and deliver more features. 3. Reduced Revenue Loss Some errors go beyond the user experience to negatively impact revenue. For example, a mistake in a signup workflow could prevent potential customers from creating an account. Even worse, many high-value workflows aren’t necessarily frequently used, meaning the errors could go unnoticed for a long time, resulting in a slow revenue bleed. Catching these errors early on is essential to avoid revenue loss. These requirements are particularly critical in e-commerce businesses where an error could mean the difference between a sale and a lost visitor. Fortunately, some error monitoring solutions make defining VIP users and workflows easy to minimize revenue loss. Best Practices for Error Monitoring Development teams have a lot of choices when it comes to error monitoring and tracking solutions. In most cases, these solutions offer the ability to track bugs, trace their root cause, and create issues. But Bugsnag goes well beyond typical error monitoring solutions to help prioritize errors and ensure the stability of each release. Increase Confidence with Stability Scores Many software organizations struggle to balance bug squashing with feature development. At the same time, DevOps teams may find it difficult to determine if a release is ready for production users. Bugsnag’s Stability Score simplifies these decisions using a single metric – the percentage of sessions without a single unhandled error. After setting a target stability (Service Level Objective) and a critical stability (Service Level Agreement) level, you can automatically monitor new releases to determine if they meet the standards. Eliminate Notification Fatigue with Smart Alerts Most people delete spam emails without even reading them. Similarly, developers receiving hundreds of irrelevant notifications are more likely to miss the important notifications in the mix. At SmartBear, we recognize that not all errors are worth fixing, and notifying developers of every error can lead to notification fatigue. That’s why we make it easy to segment errors based on the teams responsible for fixing them while ensuring the irrelevant errors don't crowd the workflow. As a result, the right developers can focus on pressing bugs. Work More Efficiently with Full-Stack Traces Software applications are becoming increasingly complex with the rise of microservices and front-end frameworks. As a result, fixing bugs has become more and more difficult for developers. Bugsnag integrates with source control tools and source maps to provide readable stack traces – even from minified or obfuscated source code. In addition, you can see a timeline of user actions and system broadcasts leading up to an error to reproduce them more quickly. And finally, you can access this data from a single dashboard. The Bottom Line Error monitoring strategies are essential in today’s hyper-competitive market. Proactively monitoring releases can ensure a robust user experience, minimize revenue loss, and enhance your team’s productivity. Bugsnag makes it easy to focus on the errors that matter, direct bug fixes to the right team members, and increase confidence in deployments.

Stories, News & Mentions about BUGSNAG

Bugsnag’s Stories on HackerNoon

Bugsnag's News & Mentions