Skip to content
Merged
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
17 changes: 2 additions & 15 deletions docs/product/explore/dropped-data.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ description: >-

<Include name="feature-available-for-user-group-limited-avail.mdx" />

When data is ingested into Sentry, it can be dropped intentionally or unintentionally for a number of reasons. Sample rate (most commonly on purpose), queue overflow, inbound filters, and invalid or malformed data are some top examples for why data might be dropped.
When data is ingested into Sentry, it can be dropped intentionally or unintentionally for a number of reasons. Sample rate (most commonly on purpose), queue overflow, inbound filters, and invalid or malformed data are some top examples for why data might be dropped.

## Troubleshooting Dropped Data
Traces, Logs, and Application Metrics charts in [Explore](/product/explore/) can show data that Sentry did not store. Hover over the dropped data line at the bottom of the chart to see the summary. Click on the line to see the details and troubleshoot.
Expand All @@ -17,7 +17,7 @@ Traces, Logs, and Application Metrics charts in [Explore](/product/explore/) can

The dropped data line leaves out data you chose to drop: everything in [Client Sampled](#category-client-sampled) and [Inbound Filters](#category-inbound-filters), plus [Disallowed Origin](#disallowed-origin), [Missing Signature](#missing-signature), and [DSN Rate Limit](#dsn-rate-limit). These reasons still appear in the details list.

Below are all the possible reasons why data might be dropped. They correspond with the title you will see when exploring dropped data in Sentry.
Below are all the possible reasons why data might be dropped. They correspond with the title you will see when exploring dropped data in Sentry.

Each reason includes what happened, why it happens, and what to change so less data is dropped. Reasons marked **Legacy** are no longer reported by current Sentry ingestion, so you'll only see them in older data.

Expand Down Expand Up @@ -1496,19 +1496,6 @@ Sentry rejected an event because its view hierarchy attachment, which mobile SDK
- **Actions:**
- Send fewer or smaller attachments with each event.

#### Switch Dying Message Too Large

Reason code: `too_large:attachment:nnswitch_dying_message`.

Sentry rejected an envelope because a Nintendo Switch dying message attachment was over the attachment size or count limits. The dying message has no count of its own, so the drop is recorded against the error event and other attachments.

- **Short:** Switch dying message hit attachment limit.
- **Causes:**
- The dying message attachment itself is too large.
- Other attachments sent with it pushed the envelope over the shared limits.
- **Actions:**
- Send fewer or smaller attachments.

### Category: Rate Limited

Sentry throttled requests or dropped events after they arrived.
Expand Down
Loading