Atlas

Learn more about Sentry's Atlas integration and how you can connect Atlas sessions directly to Sentry issues

Atlas is all-in-one customer support software built to show your customers’ experience in a simple, timeline view. Easily link Atlas sessions to Sentry issues and link Sentry issues to existing Atlas sessions.

This integration is maintained and supported by the company that created it. For more details, check out our Integration Platform documentation.

Sentry owner, manager, or admin permissions are required to install this integration.

Atlas won't work with self-hosted Sentry.

  1. Navigate to App Configuration > Sentry in Atlas

Installation flow for Sentry integration from Atlas

  1. Follow the instructions to install the Atlas app from within Sentry

Session linking allows you to associate Sentry issues with sessions in Atlas so that they can be viewed by your support team when they are assisting your customers.

Session linking is automatically attempted if a user has been identified by Sentry. However, if there are multiple simultaneous sessions, disambiguation is needed. For this reason, the best practice is to always identify Atlas sessions from Sentry.

This can be done by first getting the session id from Atlas by calling the following from the client:

Copied
apiAxios.interceptors.request.use(config => {
  config.headers['X-Atlas-Session-Id'] =
    window.Atlas?.recording?.getSessionId();
  return config;
});

You can send this to the Sentry via your Client SDK:

Copied
Sentry.addEventProcessor(event => {
  event.tags = {
    ...(event.tags || {}),
    ['atlasSupport.sessionId']: window.Atlas?.recording?.getSessionId(),
  };
  return event;
});

or from the Server SDK:

Copied
sentry_sdk.set_tag("atlasSupport.sessionId", atlas_session_id)

Now, Sentry issues will appear in the customer’s timeline in Atlas:

Sentry issues appearing on the customer timeline within Atlas

As well as within the session recording:

Sentry issues appearing on the session recording within Atlas

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").