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 error, 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.
0 Comments
Leave a Reply. |