What payload, envelope, and compression limits apply to Sentry ingestion? #66
|
What limits should a Sentry transport account for before sending envelopes or legacy store requests to Bicho? |
Replies: 1 comment
|
Bicho limits both the wire body and the decompressed request body to 2 MiB, independently. Each error event is limited to 1 MiB, and its normalized stored payload must also fit within 1 MiB. Compression cannot make an oversized expanded event acceptable. An envelope can contain at most 100 items, including unsupported items that will be discarded. Parsed JSON objects are bounded by 32 nesting levels and 20,000 structural values. Large contexts or deeply nested custom data can exceed those structural limits even if the body fits the byte limit. Requests support Malformed error events reject the batch before persistence, so a valid first event does not rescue a malformed later one. Size violations return 413; unsupported compression returns 415; malformed JSON or framing can return 400. Reducing envelope size alone will not fix a single oversized event. Trim unnecessary context at capture time and inspect the actual response before treating the failure as retryable. Documentation - Move from Sentry Source - Bicho: Sentry ingestion |
Bicho limits both the wire body and the decompressed request body to 2 MiB, independently. Each error event is limited to 1 MiB, and its normalized stored payload must also fit within 1 MiB. Compression cannot make an oversized expanded event acceptable.
An envelope can contain at most 100 items, including unsupported items that will be discarded. Parsed JSON objects are bounded by 32 nesting levels and 20,000 structural values. Large contexts or deeply nested custom data can exceed those structural limits even if the body fits the byte limit.
Requests support
gzipanddeflatethroughContent-Encoding. Brotli,zstd, and base64-wrapped legacy bodies are unsupported. The legacy/storeroute…