Dokumentation

OpenErrorAPI taler Sentry-wire-protokollen, så du beholder den officielle SDK du allerede bruger og ændrer én linje: DSN. Denne side viser hvordan, og — lige så vigtigt — hvad vi ikke understøtter.

Skift fra Sentry på 10 minutter

Der er ingen SDK at udskifte og ingen kode at omskrive. Du peger den SDK du allerede har på en anden DSN.

  1. 1

    Opret et projekt i konsollen. Du får en DSN i formen https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID.

  2. 2

    Udskift DSN i din eksisterende Sentry.init() — normalt én environment variable. Behold SDK'en, versionen og alle indstillinger du allerede har sat.

  3. 3

    Deploy og udløs én fejl. Den vises i konsollen inden for et sekund, grupperet som den var i Sentry.

PHP

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

JavaScript / TypeScript

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

Node.js

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

Python

pip install sentry-sdk
sentry_sdk.init(dsn="https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID")

Go

go get github.com/getsentry/sentry-go
sentry.Init(sentry.ClientOptions{Dsn: "https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID"})

Dart / Flutter

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

Uploader du allerede source maps med sentry-cli? Behold det trin også — sæt SENTRY_URL til https://openerrorapi.com og brug et upload token som SENTRY_AUTH_TOKEN.

Sentry-kompatibilitet, ærligt

Kompatibilitet er hele løftet, hvilket gør det til den farligste ting at overdrive. Denne tabel er genereret fra samme kilde som koden og vores maskinlæsbare dokumentation bruger, så den kan ikke stille og roligt afvige fra virkeligheden.

7 områder fuldt understøttet · 3 delvis · 3 ikke understøttet.

Område Status Detalje
Envelope ingest (/api/{id}/envelope/) Understøttet 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/) Understøttet Legacy endpoint for older SDKs. Same processing pipeline as envelopes.
Error events & grouping Understøttet Exceptions, messages, stack traces, tags, user, contexts, breadcrumbs, request. Grouping by fingerprint with an explicit `fingerprint[]` override.
Sessions / release health Understøttet Session envelope items are processed; crash-free sessions and users are shown per release. Available from the Team plan.
Security reports (CSP) Understøttet 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 Understøttet 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 Delvis 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 Understøttet Embeddable widget; reports land next to the errors they belong to.
Transactions / performance Delvis 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) Ikke understøttet Not processed yet. Log items are ignored, which does not affect error reporting from the same SDK.
Cron monitors (check_in items) Delvis 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 Ikke understøttet Deliberately out of scope. These are the reasons to stay on Sentry; we do not pretend otherwise.
Native symbolication (dSYM / ProGuard) Ikke understøttet Not supported. Native mobile crashes arrive, but stay unsymbolicated.

Gå videre

AI-agent API & MCP

Komplet reference til autonome agenter: MCP server, sessionsnøgler, scopes og hvad en agent aldrig må gøre.

llms.txt

Maskinlæsbar opsummering af denne side til LLM'er, efter llms.txt-konventionen.

Konsol

Issues, releases, advarsler, monitorer og dine DSN-nøgler.