---
title: Inspect errors in a session replay
description: "Correlate user actions with console logs, JavaScript errors, and network requests in a session replay."
product: session-replay
lang: en
token_estimate: 928
---
# Inspect errors in a session replay

> For AI agents: a documentation index is available at [/docs/llms.txt](/docs/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

Inspect console logs and network requests alongside a session replay to identify technical failures during a user's interaction. Use the replay to locate a failure in one session, then analyze error events in charts to measure its impact across users.

## Prerequisites

Error Analytics requires these SDK versions:

| Feature | SDK | Minimum version |
| --- | --- | --- |
| Console errors | [Session Replay Browser SDK](https://amplitude.com/docs/sdks/session-replay/session-replay-standalone-sdk) (`@amplitude/session-replay-browser`) | 1.22.4 |
| Console errors | [Session Replay Browser SDK Plugin](https://amplitude.com/docs/sdks/session-replay/session-replay-plugin) (`@amplitude/plugin-session-replay-browser`) | 1.16.6 |
| Network errors | [Analytics Browser SDK](https://amplitude.com/docs/sdks/analytics/browser/browser-sdk-2) (`@amplitude/analytics-browser`) | 2.24.0 |

Enable [console tracking in Session Replay settings](https://amplitude.com/docs/session-replay/session-replay-settings#console-tracking) to capture console messages, warnings, and errors.

Error Analytics covers JavaScript console logs, failed network requests and API calls, and runtime JavaScript errors. Network error capture uses the Analytics Browser SDK listed in the requirements table.

## View console logs in a replay

1. [Open a session replay](https://amplitude.com/docs/session-replay/find-replays) from a chart, User Look-Up, or the Session Replay list.
2. Select the console icon to expand the console log view.
3. Select a log entry to jump to that moment in the replay.

The console panel shows logs, warnings, and errors in chronological order alongside the session timeline. Network errors display at the bottom of the replay modal.

## Inspect network requests

Open the **Network** tab in the viewer's _DevTools_ section. Each request shows its URL, HTTP method, status code, and response time. Select a row to open its detail panel.

| Tab | Contents |
| --- | --- |
| Headers | The request URL, HTTP method, status code, and captured request and response headers. |
| Payload | The captured request body. This tab appears only when you configure a `requestBody` capture rule in your SDK settings. |
| Response | The captured response body. This tab appears only when you configure a `responseBody` capture rule in your SDK settings. |
| Timing | When the request started relative to the replay and how long it took, with a waterfall visualization. |

To capture request and response bodies, configure `requestBody` and `responseBody` capture rules in `networkTracking`. Follow [Track network requests](https://amplitude.com/docs/sdks/analytics/browser/browser-sdk-2#track-network-requests) in the Analytics Browser SDK reference.

Use the Network and Console tabs together to correlate user actions with API calls and JavaScript logs. For example, if checkout fails, check whether the payment API call returned a non-200 status code at that moment.

## Analyze error events

Error events appear in the event stream. You can:

- Use [Event Segmentation](https://amplitude.com/docs/analytics/charts/event-segmentation/event-segmentation-build) to measure error frequency and trends.
- Include error events in [Funnel Analysis](https://amplitude.com/docs/analytics/charts/funnel-analysis/funnel-analysis-build) to measure their impact on conversion.
- [Filter session replays](https://amplitude.com/docs/session-replay/find-replays#search-for-a-replay) by error events to investigate affected sessions.