SDKs are configurable using a variety of options. The options are largely standardized among SDKs, but there are some differences to better accommodate platform peculiarities. Options are set when the SDK is first initialized.
Options are passed to the
init() function as optional keyword arguments:
import sentry_sdk sentry_sdk.init( dsn="https://examplePublicKey@o0.ingest.sentry.io/0", max_breadcrumbs=50, debug=True, # Set traces_sample_rate to 1.0 to capture 100% # of transactions for performance monitoring. # We recommend adjusting this value in production, traces_sample_rate=1.0, # By default the SDK will try to use the SENTRY_RELEASE # environment variable, or infer a git commit # SHA as release, however you may want to set # something more human-readable. # release="email@example.com", )
The list of common options across SDKs. These work more or less the same in all SDKs, but some subtle differences will exist to better support the platform. Options that can be read from an environment variable (
SENTRY_RELEASE) are read automatically.
SENTRY_DSN environment variable. If that variable also does not exist, the SDK will just not send any events.
In runtimes without a process environment (such as the browser) that fallback does not apply.
Learn more about DSN utilization.
Turns debug mode on or off. If debug is enabled SDK will attempt to print out useful debugging information if something goes wrong with sending the event. The default is always
false. It's generally not recommended to turn it on in production, though turning
debug mode on will not cause any safety concerns.
Sets the release. Some SDKs will try to automatically configure a release out of the box but it's a better idea to manually set it to guarantee that the release is in sync with your deploy integrations or source map uploads. Release names are strings, but some formats are detected by Sentry and might be rendered differently. Learn more about how to send release data so Sentry can tell you about regressions between releases and identify the potential source in the releases documentation or the sandbox.
By default the SDK will try to read this value from the
SENTRY_RELEASE environment variable (in the browser SDK, this will be read off of the
window.SENTRY_RELEASE if available).
Sets the environment. This string is freeform and set to
production by default. A release can be associated with more than one environment to separate them in the UI (think
production or similar).
By default the SDK will try to read this value from the
SENTRY_ENVIRONMENT environment variable.
Configures the sample rate for error events, in the range of
1.0. The default is
1.0 which means that 100% of error events are sent. If set to
0.1 only 10% of error events will be sent. Events are picked randomly.
This variable controls the total amount of breadcrumbs that should be captured. This defaults to
100, but you can set this to any number. However, you should be aware that Sentry has a maximum payload size and any events exceeding that payload size will be dropped.
When enabled, stack traces are automatically attached to all messages logged. Stack traces are always attached to exceptions; however, when this option is set, stack traces are also sent with messages. This option, for instance, means that stack traces appear next to all log messages.
This option is turned off by default.
Grouping in Sentry is different for events with stack traces and without. As a result, you will get new groups as you enable or disable this flag for certain events.
If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
If you are using Sentry in your mobile app, read our frequently asked questions about mobile data privacy to assist with Apple App Store and Google Play app privacy details.
This option is turned off by default.
If you enable this option, be sure to manually remove what you don't want to send using our features for managing Sensitive Data.
send_default_pii is turned off, scrubs the event payload for sensitive information from a
denylist. See how to configure the scrubber here.
When enabled, source context will be included in events sent to Sentry. This source context includes the five lines of code above and below the line of code where an error happened.
The option is enabled by default.
When enabled, the SDK will capture a snapshot of local variables to send with the event to help with debugging.
This option is on by default.
This option can be used to supply a "server name." When provided, the name of the server is sent along and persisted in the event. For many integrations, the server name actually corresponds to the device hostname, even in situations where the machine is not actually a server.
Most SDKs will attempt to auto-discover this value.
A list of string prefixes of module names that belong to the app. This option takes precedence over
Sentry differentiates stack frames that are directly related to your application ("in application") from stack frames that come from other packages such as the standard library, frameworks, or other dependencies. The application package is automatically marked as
inApp. The difference is visible in sentry.io, where only the "in application" frames are displayed by default.
A list of string prefixes of module names that do not belong to the app, but rather to third-party packages. Modules considered not part of the app will be hidden from stack traces by default.
This option can be overridden using
This parameter controls whether integrations should capture HTTP request bodies. It can be set to one of the following values:
never: Request bodies are never sent.
small: Only small request bodies will be captured. The cutoff for small depends on the SDK (typically 4KB).
medium: Medium and small requests will be captured (typically 10KB).
always: The SDK will always capture the request body as long as Sentry can make sense of it.
The number of characters after which the values containing text in the event payload will be truncated (defaults to
A path to an alternative CA bundle file in PEM-format.
Has been renamed to max_request_body_size.
Has been renamed to include_local_variables.
Set this boolean to
false to disable sending of client reports. Client reports are a protocol feature that let clients send status reports about themselves to Sentry. They are currently mainly used to emit outcomes for events that were never sent.
For many platform SDKs integrations can be configured alongside it. On some platforms that happen as part of the
init() call, in some others, different patterns apply.
In some SDKs, the integrations are configured through this parameter on library initialization. For more information, please see our documentation for a specific integration.
This can be used to disable integrations that are added by default. When set to
false, no default integrations are added.
These options can be used to hook the SDK in various ways to customize the reporting of events.
This function is called with an SDK-specific message or error event object, and can return a modified event object, or
null to skip reporting the event. This can be used, for instance, for manual PII stripping before sending.
This function is called with an SDK-specific transaction event object, and can return a modified transaction event object, or
null to skip reporting the event. One way this might be used is for manual PII stripping before sending.
This function is called with an SDK-specific breadcrumb object before the breadcrumb is added to the scope. When nothing is returned from the function, the breadcrumb is dropped. To pass the breadcrumb through, return the first argument, which contains the breadcrumb object. The callback typically gets a second argument (called a "hint") which contains the original object from which the breadcrumb was created to further customize what the breadcrumb should look like.
Transports are used to send events to Sentry. Transports can be customized to some degree to better support highly specific deployments.
Switches out the transport used to send events. How this works depends on the SDK. It can, for instance, be used to capture events for unit-testing or to send it through some more complex setup that requires proxy authentication.
When set, a proxy can be configured that should be used for outbound requests. This is also used for HTTPS requests unless a separate
https-proxy is configured. However, not all SDKs support a separate HTTPS proxy. SDKs will attempt to default to the system-wide configured proxy, if possible. For instance, on Unix systems, the
http_proxy environment variable will be picked up.
Configures a separate proxy for outgoing HTTPS requests. This value might not be supported by all SDKs. When not supported the
http-proxy value is also used for HTTPS requests at all times.
A dict containing additional proxy headers (usually for authentication) to be forwarded to
Controls how many seconds to wait before shutting down. Sentry SDKs send events from a background queue. This queue is given a certain amount to drain pending events. The default is SDK specific but typically around two seconds. Setting this value too low may cause problems for sending events from command line applications. Setting the value too high will cause the application to block for a long time for users experiencing network connectivity problems.
A boolean value, if true, transactions and trace data will be generated and captured. This will set the
traces-sample-rate to the recommended default of 1.0 if
traces-sample-rate is not defined. Note that
traces-sampler take precedence over this option.
A number between 0 and 1, controlling the percentage chance a given transaction will be sent to Sentry. (0 represents 0% while 1 represents 100%.) Applies equally to all transactions created in the app. Either this or
traces_sampler must be defined to enable
A function responsible for determining the percentage chance a given transaction will be sent to Sentry. It will automatically be passed information about the transaction and the context in which it's being created, and must return a number between
0 (0% chance of being sent) and
1 (100% chance of being sent). Can also be used for filtering transactions, by returning 0 for those that are unwanted. Either this or
traces_sample_rate must be defined to enable tracing.
An optional property that controls which downstream services receive tracing data, in the form of a
sentry-trace and a
baggage header attached to any outgoing HTTP requests.
The option may contain a list of strings or regex against which the URLs of outgoing requests are matched. If one of the entries in the list matches the URL of an outgoing request, trace data will be attached to that request. String entries do not have to be full matches, meaning the URL of a request is matched when it contains a string provided through the option.
trace_propagation_targets is not provided, trace data is attached to every outgoing request from the instrumented client.
An optional list of functions that should be set up for performance monitoring. For each function in the list, a span will be created when the function is executed. Functions in the list are represented as strings containing the fully qualified name of the function.
This is a convenient option, making it possible to have one central place for configuring what functions to trace, instead of having custom instrumentation scattered all over your code base.
To learn more, see the Custom Instrumentation documentation.
When enabled, a new monitor thread will be spawned to perform health checks on the SDK. If the system is unhealthy, the SDK will keep halving the
traces_sample_rate set by you in 10 second intervals until recovery. This downsampling helps ensure that the system stays stable and reduces SDK overhead under high load.
This option is enabled by default.