Bugsnag

The FullStory integration with Bugsnag lets you see the FullStory session associated with the JavaScript exception. If you haven't already, sign up for Bugsnag

This feature is not supported on FullStory for Mobile Apps. 

Installation

After you setup your Bugsnag account, make sure the Bugsnag script is installed.

  1. Login to FullStory
  2. Navigate to Settings > Integrations 
  3. Toggle on Bugsnag under Available Integrations

2020-08-20_at_1.02_PM.png

Now, when you open a Javascript exception in Bugsnag, you'll see a FullStory tab containing a clickable playback link to the session in which the Javascript exception occurred.

2020-08-20_at_1.02_PM2.png

If you would like to be linked directly to the exact moment in the session that the Javascript exception occurred, you can modify your Bugsnag implementation code. Here's some sample code, that was passed along to us by Bugsnag support, to help you get started.

Note: This is for the latest version (v7) of Busgnag JS. See below for the legacy version.
Bugsnag.start({
apiKey: 'YOUR_API_KEY',
onError: function (event) {
// Make sure FullStory object exists.
if (window.FS && window.FS.getCurrentSessionURL) {
event.addMetadata('fullstory', {
urlAtTime: window.FS.getCurrentSessionURL(true)
})
}
}
})

If you're using version 6 of the Bugsnag JS API, use the following code to create the Bugsnag client.

window.bugsnagClient = bugsnag({
    apiKey: 'API KEY',
    beforeSend: function (report) {
        // Make sure FullStory object exists.
        if (window.FS && window.FS.getCurrentSessionURL) {
            report.updateMetaData('fullstory', {'urlAtTime': window.FS.getCurrentSessionURL(true)});
       }
    }
});

Need to get in touch with us?

The FullStory Team awaits your every question.

Contact us