From 12397af53d93802de2a819528cee6405481c1f6c Mon Sep 17 00:00:00 2001 From: Martin Linzmayer Date: Thu, 12 Jun 2025 16:01:41 +0200 Subject: [PATCH 1/2] Add new discard reason description --- docs/product/stats/index.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/product/stats/index.mdx b/docs/product/stats/index.mdx index 793a5d1bd6f98..9f51be135a163 100644 --- a/docs/product/stats/index.mdx +++ b/docs/product/stats/index.mdx @@ -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, typically because the 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. @@ -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. \ No newline at end of file +[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. From df897e951dbfbdf78ec33335539cb7ed5d683007 Mon Sep 17 00:00:00 2001 From: Martin Linzmayer Date: Thu, 12 Jun 2025 16:07:24 +0200 Subject: [PATCH 2/2] wording --- docs/product/stats/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/product/stats/index.mdx b/docs/product/stats/index.mdx index 9f51be135a163..5197894ac9e4c 100644 --- a/docs/product/stats/index.mdx +++ b/docs/product/stats/index.mdx @@ -65,7 +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, typically because the 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. +- **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.