Skip to content
CloseYourItdocsPages
Back to the siteENITSelf-host

Documentation / Connect / Connect your apps

Sentry SDK

Send errors with a compatible Sentry SDK; sessions and crashes have separate profiles.

What it collects

The error profile accepts events and messages from compatible Sentry SDKs. It retains causes, frames and release information according to the verified profile. This is not compatibility with every Sentry feature or version.

The backend also implements separate session and native crash report profiles. Sessions were exercised with Python sentry-sdk 2.71.0; crashes with Sentry Native 0.17.1 on Linux arm64. An SDK's error compatibility does not establish those other signals.

Logs, general metrics, Sentry transactions, page views and Sentry replay do not become supported by changing a DSN. Use native SDKs or OpenTelemetry for their respective channels.

Configure

Copy the compatible DSN from the project settings: use its public key and the installation's numeric Sentry project identifier, not the project's native UUID.

https://<public-key>@<your-host>/<numeric-sentry-project-id>

Pass it to your SDK according to its installed-version guide. A secret server bearer must never enter browser code or a distributed application.

Verify the profile

Send a controlled error and verify storage in the intended project and release. For session health and stack reconstruction, also check compatible backend builds, processors and artifacts. Successful delivery does not establish symbol reconstruction.