Capturing sessions

BugSnag tracks the number of “sessions” that happen within your application. This allows you to compare stability scores between releases and helps you to understand the quality of your releases.

Sessions are captured and reported by default. This behavior can be disabled using the autoTrackSessions configuration option.

Automatic tracking

Browser

In the browser, BugSnag will automatically report a session each time:

• The page loads
• The URL changes via history.pushState() or history.replaceState()

Node.js

Sessions are reported in Node.js every time a request is served if you are using one of the server integrations:

• @bugsnag/plugin-express
• @bugsnag/plugin-restify
• @bugsnag/plugin-koa

A summary of sessions recorded will be periodically sent to BugSnag.

Manual session handling

If you want control over what is deemed a session, you can switch off automatic session tracking with the autoTrackSessions option, and manage the session lifecycle using startSession(), pauseSession() and resumeSession() on the Bugsnag client.

As of v8 of the BugSnag SDK, calling methods on the Bugsnag client inside middleware of a Node app is request-specific and so only affects the request being handled. See our Node.js guide for more details.

startSession

Starts a new session to which subsequent handled and unhandled events will be attributed to.

If there is already an active session, it will be replaced with a new one. Use resumeSession if you only want to start a session when one doesn’t already exist.

Bugsnag.startSession()

// this starts a session
var sessionClient = Bugsnag.startSession()

// this error is reported with session information
sessionClient.notify(new Error('boom'))

// this error is not reported with session information
// because it uses the original client
Bugsnag.notify(new Error('bam'))

pauseSession

Prevents further events being attributed to the current session until the session is resumed or a new session is started.

A client object is returned for use in multi-user processes, see notes in startSession.

Bugsnag.pauseSession()

resumeSession

Resumes tracking events against the current session, if it was previously paused. If there is was no previous session, a new session is started. This method returns true if there was a session to resume or false if a new session was created.

A client object is returned for use in multi-user processes, see notes in startSession.

Bugsnag.resumeSession()

Discarding and amending sessions

The data captured in a session can be customized by adding an onSession callback as part of your BugSnag configuration.

Bugsnag.start({
  onSession: function (session) {
    var userId = getMyUserIdentifier() // a custom user resolver
    session.setUser(userId)
  }
})

As with an onError callback, the return value from onSession determines whether the session will be delivered to BugSnag and so can be used to discard sessions if required.

Adding and removing callbacks

We recommend adding callbacks through the onSession configuration option to ensure that it is registered as soon as BugSnag starts. However, the following methods are provided to allow callbacks to be added and removed whilst the application is running:

var cb = function(session) { /* ... */ };
Bugsnag.addOnSession(cb);
...
Bugsnag.removeOnSession(cb);

As of v8 of the BugSnag SDK, calling methods on the Bugsnag client inside middleware of a Node app is request-specific and so only affects the request being handled. See our Node.js guide for more details.

The Session object

The following information is available on a Session object, the representation of session information available in an onSession callback.