Skip to content

Add new discard reason description #14018

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/product/stats/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,7 @@ Events and attachments might be discarded if they don't match the expected forma
- **Empty**: An empty request or a request missing its primary data component was submitted.
- **Invalid Data**: Data sent by the SDK was invalid and does not meet the basic schema. This likely indicates an SDK implementation bug. Please report a bug if this issue persists.
- **Invalid Request**: The HTTP submission was invalid or was missing required information. This is likely due to a problem in the SDK implementation. Please report a bug if this issue persists.
- **Invalid Signature**: A signature was invalid or missing from the request. This is likely because the local relay is not in the trusted list or is running an outdated version, or because the data was sent directly to Sentry by an SDK.
- **Minidump**: The minidump in a minidump upload request was missing or invalid. See the [Minidumps documentation](/platforms/native/guides/minidumps/) for details on how to upload minidumps.
- **Payload**: The HTTP submission was incomplete and could not be processed. This is likely due to a network failure.
- **Project Missing**: The specified Sentry project is disabled or project information in the submitted request was inconclusive.
Expand Down Expand Up @@ -165,4 +166,4 @@ The "Number of Releases" chart and table show the releases that were created for

#### Dropped Profile Hours

[Relay](/product/relay/) calculates profile durations for accepted outcomes rather than for every profile chunk received. Both profile hours and UI profile hours stats are derived from these accepted profile chunks or UI profile chunks, respectively, with no duration data stored for dropped outcomes (which are simply counted). Each profile chunk has a maximum duration of 66 seconds. Based on internal testing data the 10th and 25th percentiles of accepted profile chunk durations are approximately 9.9 seconds. This metric was used to select 9.0 seconds as the estimation multiplier for each dropped profile chunk.
[Relay](/product/relay/) calculates profile durations for accepted outcomes rather than for every profile chunk received. Both profile hours and UI profile hours stats are derived from these accepted profile chunks or UI profile chunks, respectively, with no duration data stored for dropped outcomes (which are simply counted). Each profile chunk has a maximum duration of 66 seconds. Based on internal testing data the 10th and 25th percentiles of accepted profile chunk durations are approximately 9.9 seconds. This metric was used to select 9.0 seconds as the estimation multiplier for each dropped profile chunk.