Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Sentry has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 2 scoped observations for Sentry. The baseline covers attachment request size, attachment retention. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| attachment request sizeThe crash report, when present, counts in the uncompressed event total. | 20 MB compressed request; 100 MB uncompressed per event | Events with attachments | SentryAug 22, 2026 |
| attachment retentionAttachments stop storing when the included storage quota is exceeded. | 30 days | Stored event attachments | SentryAug 22, 2026 |
Tracked constraints and impact
Event attachment request, uncompressed payload, retention, and quota behavior. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
Sentry Event Attachment Size Limits
Sentry Event Attachment Size Limits, verified against Sentry's official documentation with scope, implementation impact, caveats, and a direct check.
Sentry Attachment Retention & Quota
Sentry Attachment Retention & Quota, verified against Sentry's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current Sentry baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Compressed request, uncompressed event, retention, and 413 limits