Interface Hub

Records a new breadcrumb which will be attached to future events.

Breadcrumbs will be added to subsequent events to provide more context on user's actions prior to an error or crash.

This binds the given client to the current scope.

Captures a manually created event and sends it to Sentry.

Captures an exception event and sends it to Sentry.

Captures a message event and sends it to Sentry.

Sends the current session on the scope to Sentry

Callback to set context information onto the scope.

Ends the session that lives on the current scope and sends it to Sentry

Returns the client of the top stack.

Returns the integration if installed on the current client.

Returns the scope of the top stack

This is the getter for lastEventId.

Removes a previously pushed scope from the stack.

This restores the state before the scope was pushed. All breadcrumbs and context information added since the last call to this.pushScope are discarded.

Create a new scope to store context information.

The scope will be layered on top of the current one. It is isolated, i.e. all breadcrumbs and context information added to this scope will be removed once the scope ends. Be sure to always remove this scope with this.popScope when the operation finishes or throws.

For the duration of the callback, this hub will be set as the global current Hub. This function is useful if you want to run your own client and hook into an already initialized one e.g.: Reporting issues to your own sentry when running in your component while still using the users configuration.

Sets context data with the given name.

Set key:value that will be sent as extra data with the event.

Set an object that will be merged sent as extra data with the event.

Set key:value that will be sent as tags data with the event.

Can also be used to unset a tag, by passing undefined.

Set an object that will be merged sent as tags data with the event.

Updates user context information for future events.

Returns if default PII should be sent to Sentry and propagated in ourgoing requests when Tracing is used.

Starts a new Session, sets on the current scope and returns it.

To finish a session, it has to be passed directly to client.captureSession, which is done automatically when using hub.endSession() for the session currently stored on the scope.

When there's already an existing session on the scope, it'll be automatically ended.

Starts a new Transaction and returns it. This is the entry point to manual tracing instrumentation.

A tree structure can be built by adding child spans to the transaction, and child spans to other spans. To start a new child span within the transaction or any span, call the respective .startChild() method.

Every child span must be finished before the transaction is finished, otherwise the unfinished spans are discarded.

The transaction must be finished with a call to its .finish() method, at which point the transaction with all its finished child spans will be sent to Sentry.

Returns all trace headers that are currently on the top scope.

Creates a new scope with and executes the given operation within. The scope is automatically removed once the operation finishes or throws.

This is essentially a convenience function for:

pushScope();
callback();
popScope();
Copy