Documentation

Switch from Sentry in 10 minutes

There is no SDK to replace and no code to rewrite. You point the SDK you already have at a different DSN.

1. 1

   Create a project in the console. You get a DSN in the form https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID.

2. 2

   Replace the DSN in your existing Sentry.init() — usually one environment variable. Keep the SDK, the version and every option you already set.

3. 3

   Deploy and trigger one error. It shows up in the console within a second, grouped like it was in Sentry.

composer require sentry/sentry

\Sentry\init(['dsn' => 'https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID']);

npm i @sentry/browser

Sentry.init({ dsn: 'https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID' });

npm i @sentry/node

Sentry.init({ dsn: 'https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID' });

pip install sentry-sdk

sentry_sdk.init(dsn="https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID")

go get github.com/getsentry/sentry-go

sentry.Init(sentry.ClientOptions{Dsn: "https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID"})

flutter pub add sentry_flutter

await SentryFlutter.init((o) => o.dsn = 'https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID');

Already uploading source maps with sentry-cli? Keep that step too — set SENTRY_URL to https://openerrorapi.com and use an upload token as SENTRY_AUTH_TOKEN.

Sentry compatibility, honestly

Compatibility is the whole promise, which makes it the most dangerous thing to overstate. This table is generated from the same source the code and our machine-readable docs use, so it cannot quietly drift from reality.

7 areas fully supported · 3 partial · 3 not supported.