Find Dropped Events
find_dropped_eventsIdentify events Sentry dropped before storage—from sampling, filters, rate limits, or quotas—and compare dropped vs. accepted volume to explain missing or flat data.
Instructions
Find events Sentry dropped before storing them (SDK sampling, filters, rate limits, quota, spike protection), as dropped and accepted volume over time by outcome and reason. Each drop is tagged intentional (sampling, filters) or unintentional (quota, abuse). Use it to explain flat, low, or missing data that searches, charts, and dashboards cannot show; no drops means the data is complete.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "find_dropped_events"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | ||
| fresh | No | Bypass cached reads. | |
| start | No | ||
| reason | No | ||
| dataset | No | Data type to report drops for. | spans |
| outcome | No | ||
| interval | No | ||
| regionUrl | No | ||
| projectSlug | No | ||
| statsPeriod | No | ||
| organizationSlug | No | The organization slug, from `find_organizations`. In `org/project` notation, the part before the slash. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| dataset | Yes | ||
| interval | Yes | ||
| droppedEvents | Yes | ||
| acceptedEvents | Yes |