Dokumentation
OpenErrorAPI pratar Sentry-protokollet, så du behåller den officiella SDK du redan använder och ändrar en rad: DSN. Den här sidan förklarar hur, och — lika viktigt — vad vi inte stödjer.
Byt från Sentry på 10 minuter
Det finns ingen SDK att byta ut och ingen kod att skriva om. Du pekar den SDK du redan har mot en annan DSN.
-
1
Skapa ett projekt i konsolen. Du får en DSN i formatet https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID.
-
2
Byt ut DSN i din befintliga Sentry.init() — vanligtvis en miljövariabel. Behåll SDK:n, versionen och alla inställningar du redan har.
-
3
Deploya och trigga ett fel. Det dyker upp i konsolen inom en sekund, grupperat som det var i Sentry.
PHP
composer require sentry/sentry\Sentry\init(['dsn' => 'https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID']);JavaScript / TypeScript
npm i @sentry/browserSentry.init({ dsn: 'https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID' });Node.js
npm i @sentry/nodeSentry.init({ dsn: 'https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID' });Python
pip install sentry-sdksentry_sdk.init(dsn="https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID")Go
go get github.com/getsentry/sentry-gosentry.Init(sentry.ClientOptions{Dsn: "https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID"})Dart / Flutter
flutter pub add sentry_flutterawait SentryFlutter.init((o) => o.dsn = 'https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID');Laddar du redan upp source maps med sentry-cli? Behåll det steget också — sätt SENTRY_URL till https://openerrorapi.com och använd en upload-token som SENTRY_AUTH_TOKEN.
Sentry-kompatibilitet, ärligt
Kompatibilitet är hela löftet, vilket gör det till det farligaste att överdriva. Den här tabellen genereras från samma källa som koden och vår maskinläsbara dokumentation använder, så den kan inte tyst avvika från verkligheten.
7 områden fullt stödda · 3 partiellt · 3 ej stödda.
| Område | Status | Detalj |
|---|---|---|
Envelope ingest (/api/{id}/envelope/) |
Stöds | The modern endpoint every current SDK uses. Gzip/deflate bodies, multiple items per envelope, all three auth methods (X-Sentry-Auth header, querystring, envelope dsn header). |
Store ingest (/api/{id}/store/) |
Stöds | Legacy endpoint for older SDKs. Same processing pipeline as envelopes. |
| Error events & grouping | Stöds | Exceptions, messages, stack traces, tags, user, contexts, breadcrumbs, request. Grouping by fingerprint with an explicit `fingerprint[]` override. |
| Sessions / release health | Stöds | Session envelope items are processed; crash-free sessions and users are shown per release. Available from the Team plan. |
| Security reports (CSP) | Stöds | CSP violation reports are stored and grouped like any other issue. Point report-uri at /api/{project_id}/security/?sentry_key={PUBLIC_KEY} — the browser cannot send headers, so the key goes in the URL. Both the classic csp-report body and the Reporting API array are accepted. |
| Source maps | Stöds | Upload via our API, from the console, or with sentry-cli. Frames are de-minified on read, so uploading a map fixes old events too. |
sentry-cli |
Partiellt | Releases (new / finalize / set-commits) and source-map upload work unchanged. Chunked upload is not implemented — sentry-cli detects that and falls back to the regular upload automatically. |
| User feedback widget | Stöds | Embeddable widget; reports land next to the errors they belong to. |
| Transactions / performance | Partiellt | Transaction envelope items are accepted so SDKs do not error, but we do not build a performance product on top of them. If you need distributed tracing, keep Sentry — we are an error tracker. |
Logs (log envelope items) |
Stöds ej | Not processed yet. Log items are ignored, which does not affect error reporting from the same SDK. |
Cron monitors (check_in items) |
Partiellt | We have our own cron/heartbeat monitoring in the console, but the Sentry `check_in` envelope item is not wired to it yet. |
| Profiling, session replay | Stöds ej | Deliberately out of scope. These are the reasons to stay on Sentry; we do not pretend otherwise. |
| Native symbolication (dSYM / ProGuard) | Stöds ej | Not supported. Native mobile crashes arrive, but stay unsymbolicated. |