Sentry can drop data before storing it. Some of this is on purpose, like your SDK sample rate or inbound filters you've set up. Some isn't, like SDK queue overflows, network errors, rate limits, or invalid or malformed data.
Where to see it
When Sentry drops data for unexpected reasons, Explore shows a dropped data line under charts for Traces, Logs, and Application Metrics.
Hover over the dropped data line at the bottom of the chart to see a summary.
Click the line to open the details and see each reason data was dropped.
Next to any reason, select Ask Seer for help figuring out the cause and what to change.
Here's an example (see the yellow 'underline' right beneath the bar chat):
Data you chose to drop, like client-side sampling and inbound filters, doesn't count toward the dropped data line, but it still shows up in the details list.
Common reasons data is dropped
Client Sampled: Your SDK dropped data because of your configuration, like
beforeSend,ignoreSpans, or your sample rate.Client Discard: Your SDK dropped data before it left your app, for example because of a full send queue, network errors, or ad blockers.
Rate Limited: Data went over a quota, spike protection, or a DSN rate limit.
Inbound Filters: Sentry filtered out data based on your project's inbound filter settings.
Invalid or Malformed: Sentry got the data but couldn't accept it, for example because of bad timestamps, invalid JSON, or an outdated SDK.
Every reason, with its causes and recommended fixes, is listed in Investigate Dropped Data in Sentry.
This feature is rolling out and may not be available for your organization yet.