Identifying crashes at launchД«y default Bugsnag will identify crashes that occur whilst your app is launching, allowing you to prioritize fixing high-impact launch crashes.ДЇollow the Identifying crashes at launch guide to configure this functionality.// In the renderer process. addFeatureFlag ( 'New checkout flow' )ДЇor more information, see Feature flags & experiments. addFeatureFlag ( 'Checkout button color', 'Blue' ) Bugsnag. You can use the Features dashboard to identify whether these features have introduced errors into your app. Monitor errors as you roll out features or run experiments and A/B tests by declaring your feature flag and experiment usage in the Bugsnag client. This behavior can be disabled using the autoTrackSessions configuration option.Д«ugsnag will automatically report a session each time the app is launched or enters the foreground after being in the background for at least 60 seconds.ДЇor more information about or to customize session tracking, see Capturing sessions. Sessions are captured and reported by default. This allows you to compare stability scores between releases and helps you to understand the quality of your releases. Session trackingД«ugsnag tracks the number of вЂњsessionsвЂќ that happen within your application. Additional data can also be attached to breadcrumbs by providing the optional metadata parameter.ДЇor more information and examples for how custom breadcrumbs can be integrated, see Customizing breadcrumbs. leaveBreadcrumb ( 'Button clicked' )Д«ugsnag will keep track of the time and order of the breadcrumbs and show them on your dashboard.

You can use the leaveBreadcrumb method to log potentially useful events in your own applications: Bugsnag.

Power state changes, like switching to battery powerДЇor more information or to disable particular classes of automatic breadcrumb generation see configuration options.

Display added, removed, and resized events.

Automatically captured breadcrumbsД«y default, Bugsnag captures the following events as breadcrumbs: A configurable number of breadcrumbs are attached to each error report to help diagnose what events led to the error. In order to understand what happened in your application before each crash, it can be helpful to leave short log statements that we call breadcrumbs. setUser ( '3', , 'Erina' )ДЇor information on doing so, see Adding user data. You can set the user information of an error report using the user configuration property when Bugsnag starts or using tUser(): Bugsnag. In order to correlate errors with customer reports, or to see a list of users who experienced each error, it is helpful to capture and display user information on your Bugsnag dashboard. start ()ДЇor more information, see Customizing error reports. Start Bugsnag along with any renderer-specific configuration as needed: Bugsnag. When it is true, require() works as it does in Node.js. When webPreferences.nodeIntegration is false, a bundler (such as Webpack) is necessary to resolve dependencies in renderer code.

Electron api capture page