Dokumentácia

OpenErrorAPI používa Sentry wire protokol, takže ponecháš oficiálne SDK, ktoré už používaš, a zmeníš jeden riadok: DSN. Táto stránka hovorí ako, a — rovnako dôležité — čo nepodporujeme.

Prejdite zo Sentry za 10 minút

Nemusíte nahrádzať SDK ani prepisovať kód. Stačí presmerovať SDK, ktoré už používate, na iný DSN.

  1. 1

    Vytvorte projekt v konzole. Dostanete DSN vo forme https://PUBLIC_KEY@openerrorapi.com/PROJECT_ID.

  2. 2

    Nahraďte DSN v existujúcom Sentry.init() — zvyčajne jednu premennú prostredia. Ponechajte SDK, verziu a všetky nastavenia, ktoré už máte.

  3. 3

    Nasaďte a vyvolajte jednu chybu. Zobrazí sa v konzole do sekundy, zoskupená ako v 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');

Už nahrávate source mapy pomocou sentry-cli? Ponechajte aj tento krok — nastavte SENTRY_URL na https://openerrorapi.com a použite upload token ako SENTRY_AUTH_TOKEN.

Sentry kompatibilita, úprimne

Kompatibilita je celý sľub, čo z niej robí najnebezpečnejšiu vec na preháňanie. Táto tabuľka je generovaná z rovnakého zdroja, ktorý používa kód a naša strojovo čitateľná dokumentácia, takže nemôže nenápadne odbočiť od reality.

7 oblastí plne podporovaných · 3 čiastočne · 3 nepodporovaných.

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

Ďalšie kroky

AI agent API & MCP

Úplná referencia pre autonómnych agentov: MCP server, session kľúče, rozsahy a čo agent nikdy nesmie urobiť.

llms.txt

Strojovo čitateľné zhrnutie tejto stránky pre LLM, podľa konvencie llms.txt.

Konzola

Problémy, vydania, upozornenia, monitory a vaše DSN kľúče.