JSDoc

JSDoc

User-Facing Sentry SDK Client.

Context data passed by the user when starting a transaction, to be used by the tracesSampler method.

References to debug images.

Holds meta information to customize the behavior of Sentry's server-side event processing.

Primitive components of a Dsn.

JSDoc

JSDoc

Event processors are used to change the event before it will be send. We strongly advise to make this function sync. Returning a PromiseLike<Event | null> will work just fine, but better be sure that you know what you are doing. Event processing will be deferred until your Promise is resolved.

JSDoc

Just an Error object with arbitrary attributes attached to it.

Data extracted from an incoming request to a node server

Internal class used to make sure we always have the latest internal functions working in case we have a version conflict.

Integration interface

Integration Class Interface

Metadata about a captured exception, intended to provide a hint as to the means by which it was captured.

Base configuration options for every SDK.

JSDoc

Event-like interface that's usable in browser and node.

Request data included in an event as sent to Sentry

Runtime Context.

Data passed to the tracesSampler function, which forms the basis for whatever decisions it might make.

Holds additional event information. Scope.applyToEvent will be called by the client before an event is sent.

JSDocs

JSDoc

Span holding trace_id, span_id

Interface holding all properties that can be set on a Span on creation.

JSDoc

JSDoc

JSDoc

Transaction "Class", inherits Span only has setName

Interface holding Transaction-specific properties

JSDoc

Location object on a service worker's self object.

JSDoc

The baggage data structure represents key,value pairs based on the baggage spec: https://www.w3.org/TR/baggage

JSDocs

Possible choices for debug images.

Anything that can be parsed into a Dsn.

Supported Sentry transport protocols in a Dsn.

A time duration.

Fractions such as percentages.

Size of information derived from bytes.

Untyped value without a unit.

Data pulled from a sentry-trace header

Contains information about how the name of the transaction was determined. This will be used by the server to decide whether or not to scrub identifiers from the transaction name, or replace the entire name with a placeholder.