How should accepted, rejected, and discarded results affect Sentry retries? #67
|
Can an HTTP 200 response still mean that some events were not stored? How should a transport handle quota failures without duplicating accepted events? |
Replies: 1 comment
|
Yes. Successful Sentry responses include Before any acceptance, quota exhaustion returns 429 with If Bicho accepts a prefix and then cannot store the next event, it returns HTTP 200 and lists the rejected remainder. Do not replay the entire accepted envelope. Standard Sentry SDKs may ignore the response body and drop the rejected remainder, so monitor rejection information as well as status codes. If a custom recovery path explicitly resends individual rejected events, preserve their original Documentation - Move from Sentry Source - Bicho: Sentry ingestion tests |
Yes. Successful Sentry responses include
acceptedevent IDs,rejectedevent IDs, anddiscardedcounts by unsupported item type. A discarded attachment or session is not a stored error, and a 200 response does not guarantee every event was accepted.Before any acceptance, quota exhaustion returns 429 with
Retry-AfterandX-Sentry-Rate-Limits; storage failure returns 503. Respect retry timing rather than immediately replaying requests. Each project's quota applies to new events per UTC hour. Duplicate event IDs within that project do not consume quota as new occurrences.If Bicho accepts a prefix and then cannot store the next event, it returns HTTP 200 and lists the rejected remainder. Do …