Other runtimes
Python, Go, Ruby, PHP, Java, and .NET Sentry SDKs on envelope or store, with raw frames, plus a store curl when you have no SDK yet.
Epure accepts official Sentry SDKs on envelope and legacy store. Change dsn. There is no @epure/* package. Open the language guide for install and init.
Which non-JS guide do I open?
| If you ship… | Package | Guide |
|---|---|---|
| Django, Flask, FastAPI, Celery | sentry-sdk | Python |
| Gin, Echo, chi, Fiber, plain Go | sentry-go | Go |
| Rails, Sinatra, Sidekiq | sentry-ruby | Ruby |
| Laravel, Symfony, Slim | sentry-php | PHP |
| Spring Boot, Quarkus, JVM services | sentry-java | Java |
| ASP.NET Core, .NET workers | Sentry (NuGet) | .NET |
JS/TS chooser: Pick your SDK · Browser · Node · Next.js.
Language matrix
Status below is parse and ingest in this repo. Fixtures live in fixtures/sentry/.
| Language | Typical SDK | Wire | Sourcemaps | Guide |
|---|---|---|---|---|
| Python | sentry-sdk | store or envelope | raw frames | Python |
| Go | sentry-go | envelope | raw frames | Go |
| PHP | sentry-php | envelope | raw frames | PHP |
| Ruby | sentry-ruby | envelope | raw frames | Ruby |
| Java | sentry-java | envelope | raw frames | Java |
| .NET | Sentry | envelope | raw frames | .NET |
iOS/Android: out of scope (no Cocoa/Android fixtures, no dSYM/ProGuard/NDK).
Try ingest without an SDK
Smallest path with no client. Same 202 as envelope.
Try ingest
Store JSON works for scripts, CI, and SDKs you have not wired yet.
store curl
curl -sS -D - -o /tmp/epure-ingest.json -X POST
"http://localhost:8080/api/550e8400-e29b-41d4-a716-446655440000/store/"
-H "X-Sentry-Auth: Sentry sentry_version=7, sentry_key=a1b2c3d4e5f6g7h8i9j0, sentry_secret=supersecretdevkey"
-H "Content-Type: application/json"
-d '{
"platform": "javascript",
"exception": {
"values": [{ "type": "Error", "value": "Epure try-it" }]
}
}'Expected
HTTP/1.1 202 Accepted
{ "id": "<event-uuid>" }
Then open Issues. This panel does not POST from the browser. CORS and your DSN stay on your machine.
What should I see after ingest?
202, then an issue whose title matches the exception type and value, with a stack as the SDK sent it.
Transactions, replay, profiles, and sessions are discarded. Leave those sample rates at zero when the SDK exposes them.
What is live SDK smoke vs fixtures?
Browser and Node have automated ingest E2E in CI. Other languages: envelope/store fixtures parse; live SDK smoke is not all gated in CI. File issues with SDK name + version. Do not read the matrix as 100% Sentry protocol parity.
How does user feedback work?
Are traces or replay stored?
No. Transaction, replay, profile, and session items are discarded on ingest; exception events and breadcrumbs are kept. Stacks stay as the SDK sent them, apart from JS/TS .map demangle. Leave those sample rates at zero when the SDK exposes them.