Custom contexts allow you to attach arbitrary data to an event. Often, this context is shared among any issue captured in its lifecycle. You cannot search these, but they are viewable on the issue page:

Custom contexts as viewed on the Additional Data section of an event

The best way to attach custom data is with a structured context. A context must always be an object and its values can be arbitrary.

You'll first need to import the SDK, as usual:

import * as Sentry from "@sentry/react-native";

Then, use setContext and give the context a unique name:

Sentry.setContext("character", {
  name: "Mighty Fighter",
  age: 19,
  attack_type: "melee",

There are no restrictions on context name. In the context object, all keys are allowed except for type, which is used internally.

By default, Sentry SDKs normalize nested structured context data up to three levels deep. Any data beyond this depth will be trimmed and marked using its type instead. To adjust this default, use the normalizeDepth SDK option.

Learn more about conventions for common contexts in the contexts interface developer documentation.

When sending context, consider payload size limits. Sentry does not recommend sending the entire application state and large data blobs in contexts. If you exceed the maximum payload size, Sentry will respond with HTTP error 413 Payload Too Large and reject the event. When keepalive: true is used, the request may additionally stay pending forever.

The Sentry SDK will try its best to accommodate the data you send and trim large context payloads. Some SDKs can truncate parts of the event; for more details, see the developer documentation on SDK data handling.

Some contextual data can be provided directly to captureException and captureMessage calls. Provided data will be merged with the one that is already stored inside the current scope, unless explicitly cleared using a callback method.

This functionality works in three different variations:

  1. Plain object containing updatable attributes
  2. Scope instance from which we will extract the attributes
  3. Callback function that will receive the current scope as an argument and allow for modifications

We allow the following context keys to be passed: tags, extra, contexts, user, level, fingerprint.

Sentry.captureException(new Error("something went wrong"), {
  tags: {
    section: "articles",

Explicitly clear what has been already stored on the scope:

Sentry.captureException(new Error("clean as never"), (scope) => {
  scope.setTag("clean", "slate");
  return scope;

Use Scope instance to pass the data (its attributes will still merge with the global scope):

const scope = new Sentry.Scope();
scope.setTag("section", "articles");
Sentry.captureException(new Error("something went wrong"), scope);

Use Scope instance to pass the data and ignore globally configured Scope attributes:

const scope = new Sentry.Scope();
scope.setTag("section", "articles");
Sentry.captureException(new Error("something went wrong"), () => scope);

Context is held in the current scope and thus is cleared when the scope is removed ("popped"). You can push and pop your own scopes to apply context data to a specific code block or function.

Sentry supports two different ways for unsetting context:

  1. Modifying, overwriting or clearing values on the current scope.
  2. Creating a temporary scope for capturing exceptions.

With the following snippet, the user context will be updated for all future events on the current scope:


If you want to remove data from the current scope, you can call:

Sentry.configureScope((scope) => scope.clear());

The following will only configure the user context for the error captured inside the withScope callback. The context will be automatically restored to the previous state afterwards:

Sentry.withScope(function (scope) {

To learn more about setting the Scope, see our documentation on Scopes and Hubs.

Additional Data is deprecated in favor of structured contexts.

Sentry used to support adding unstructured "Additional Data" via setExtra.

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").