# What Error Tracking does not support

The Sentry features and data that Error Tracking does not offer yet.

- **Session Replay.** Replays are answered with a one-hour rate limit for their category; the
  Replay integration can be removed.
- **Span streaming** (`traceLifecycle: "stream"`, standalone spans): not shown.
- **Cron monitors** (check-ins), **logs**, **user feedback** and **metrics**: answered with a
  one-hour rate limit for their category.
- **Native crash reports** (minidumps).
- **Inbound filters** (browser extensions, legacy browsers, localhost, by message or release).
- **Server-side data scrubbing** of error events: scrub in the SDK's `beforeSend` and keep
  `sendDefaultPii: false`.
- **Importing history from Sentry**: issues, their state, assignees and comments.
- **Suspect commits**, and comments on issues.
- **Sentry's API beyond** releases, uploads, and reading issues, events and environments: IDE
  plugins and Jira or Grafana integrations that need more do not work.
- **Negation in the events search** (`!level:error`).
- **Alert rules on tags in the console**: tag filters are set through the CLI or the API.
- **Signed webhooks**: alert webhooks carry no signature.
