# Ingestion Monitor

Track Session Replay ingestion status over time to debug capture and delivery issues.

Source: https://amplitude.com/docs/session-replay/ingestion-monitor

---

On this page

- [Tracked statuses](#tracked-statuses)
- [Troubleshooting](#troubleshooting)
- [Short or incomplete replays](#short-or-incomplete-replays)

# Ingestion Monitor

Amplitude provides the Ingestion Monitor to help debug Session Replay implementation issues by tracking Session Replay status over time.

Access the Ingestion Monitor from:

- The top-right of the Session Replay section of your project's **Users & Sessions** tab.
- Any individual replay that displays an error.

### Tracked statuses

The Ingestion Monitor displays charts with the count of each status over a time range that you select:

- Successful request (status 200)
- Throttling errors (status 429)
- Quota exceeded errors (status 402)
- Invalid session IDs

Use these charts to debug unavailable session replays and monitor the health of your Session Replay implementation.

## Troubleshooting

### Short or incomplete replays

If you see short replays (less than 10 seconds) or replays that appear incomplete, check the Ingestion Monitor for 429 throttling errors.

A 429 error means your application sends too many Session Replay requests. Amplitude throttles these requests. Because replays consist of multiple chunks of data, some chunks may not send successfully, which produces incomplete or unusually short replays.

To resolve 429 throttling errors:

1. Reduce your Session Replay sample rate to lower the request volume per second.
2. Monitor the 429 error count in the Ingestion Monitor to confirm that throttling errors decrease after you adjust the sample rate.

Was this helpful?

<!--$-->

<!--/$-->