---
title: Logs & network requests | ReplayPilot Docs
description: Console messages and network requests captured alongside every session.
canonical: https://replaypilot.com/docs/logs
---

# Logs & network requests | ReplayPilot Docs

Search docs…⌘KBrowse docs

Get started
- [Installation](/docs/getting-started)
- [What's new](/docs/whats-new)

Dashboard
- [Replays & the session player](/docs/replays)
- [Errors](/docs/errors)
- [Frustration signals](/docs/frustration)
- [Funnels](/docs/funnels)
- [Releases](/docs/releases)
- [Logs & network requests](/docs/logs)
- [Visitors](/docs/visitors)
- [Heatmaps](/docs/heatmaps)
- [Click map](/docs/click-map)
- [Cohort retention](/docs/cohorts)
- [Projects & project keys](/docs/projects)
- [Alerts](/docs/alerts)
- [Shared links](/docs/shared-links)

Integrations
- [Integrations](/docs/integrations)
- [MCP server](/docs/mcp-server)

Account & data
- [Billing & plans](/docs/billing)
- [Security & masking](/docs/security-masking)
- [Data retention & limits](/docs/retention-limits)
- [Team accounts](/docs/team-accounts)

# Logs & network requests

Console messages and network requests captured alongside every session.

## What gets captured

ReplayPilot automatically captures two kinds of log alongside every recorded session. There's nothing to set up.

- **Console messages.** Anything your app logs to the browser console: log, info, warn, and error calls.

- **Network requests.** Every request your page makes, with its method, URL, status code, and how long it took.

## What's not captured

Request and response **bodies are never captured**. ReplayPilot only stores metadata: method, URL, status code, timing, and headers.

This is a deliberate choice, not a gap we plan to close. There's no safe, generic way to redact arbitrary request and response bodies, so instead of guessing, we don't record them at all.

We also strip sensitive headers before anything leaves your visitor's browser. The snippet drops the authorization, cookie, set-cookie, and proxy-authorization headers before the log line ever reaches us.

## How we flag errors

Any network request that comes back with a status code of 400 or higher is automatically flagged as an error-level log line. That makes failed requests, like a broken API call or an expired auth token, easy to spot without digging through every entry.

## Filtering and browsing logs

The Logs page lets you narrow down what you're looking at:

- **Source**: console or network.

- **Level**: for example, only errors.

- **Project**: if you run ReplayPilot across more than one site or app.

ReplayPilot collapses similar log lines into a single entry. Expand a group to see each occurrence with its own timestamp.

## Retention and limits

How far back you can search your logs, and how many log lines your account can store in total, depend on your plan. See [Data retention & limits](/docs/retention-limits) for the exact numbers.

In short: once your account hits its plan's log volume cap, ReplayPilot keeps recording sessions normally. It just stops writing new log lines until older ones age out.

[← Releases](/docs/releases)[Visitors →](/docs/visitors)