docs
verified means we ran it and captured golden-file fixtures. expected means the SDK speaks the same wire protocol and should work, but we have not run it and will not claim that we have.
Quickstart
There is no Parsemend SDK to install. Point the Sentry SDK you already have at a Parsemend DSN.
todo — this is a stub. Full reference documentation will live on this path, not on a docs subdomain.
Three steps
- 01
Create a project
Sign up and create a project. It issues a DSN with a 32-character hex public key.
- 02
Swap the DSN
.envSENTRY_DSN=https://[email protected]/4507123 - 03
Deploy
That is the whole migration. Events arrive on the envelope endpoint with their breadcrumbs, tags, environments and releases intact.
SDK compatibility
| SDK | Tested version | Status |
|---|---|---|
| sentry/sentry (PHP) | 4.29.0 | verified |
| @sentry/node | 10.64.0 | verified |
| @sentry/browser | — | expected |
| sentry-python | — | expected |
| sentry-ruby | — | expected |
| sentry-go | — | expected |
Ingest limits
- Envelope endpoint
- POST /api/{project_id}/envelope
- Legacy endpoint
- POST /api/{project_id}/store
- Content-Encoding
- gzip, deflate, identity
- Max compressed body
- 20 MiB
- Max decompressed body
- 200 MiB
- Max item size
- 1 MiB
- Default rate limit
- 300 events / 60s per key
- Default retention
- 90 days
Brotli and zstd request bodies are rejected with a recorded invalid outcome rather than a 500. Transaction, log and check-in envelope items are accepted and dropped.
Ready to turn on the agent? Start with the four fix modes.