Large HTTP Payload
This feature is available only if you're in the Early Adopter program. Features available to Early Adopters are still in-progress and may have bugs. We recognize the irony.
If you’re interested in being an Early Adopter, you can turn your organization’s Early Adopter status on/off in General Settings. This will affect all users in your organization and can be turned back off just as easily.
Large HTTP payload issues are created when an http span has an encoded body size that exceeds a threshold.
Detection Criteria
The detector for this performance issue looks for a single http span that meets the following criteria:
- The HTTP method must be a GET, POST, DELETE, PUT, PATCH
- The HTTP url must not begin with _next/static/ or _next/data/
- The HTTP url must not end with the extensions .js, .css, .svg, .png, .mp3, .jpg, .jpeg
Once an HTTP span that meets this criteria is found, the encoded body size is checked against a threshold. If Sentry isn't detecting a Large HTTP Payload issue where you expect one, it's probably because the transaction didn't meet one of the above criteria.
Span Evidence
You can find additional information about your Large HTTP Payload problem by four main aspects in the "Span Evidence" section:
- Transaction name
- Large HTTP Payload Span: The large HTTP span, usually containing the asset url.
- Payload Size: The size of the payload in bytes.
View it by going to the Issues page in Sentry, selecting your project, clicking on the Large HTTP Payload issue you want to examine, then scrolling down to the "Span Evidence" section in the "Details" tab.
Fixing Large HTTP Payload Issues
The reasons for getting consecutive Large HTTP Payload issues vary, but here are some suggestions to help you resolve them:
- If you have control over the backend, check if you're sending more data than you need or if the data can be processed further before being sent to the client.
- If all the endpoint data is needed, consider methods such as pagination to split up data across views.
- Check if any changes were made to your serializer that may have resulted in a larger body size than necessary.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").