Network Logs
Inspect HTTP requests and responses captured with extension and replay sessions to debug API and loading issues.
Network logs show what your app sent and received during a session. Use them to debug API failures, auth issues, and slow pages.
Availability
Network logs are only available for certain capture types:
✅ Chrome extension recordings
✅ Replay-style captures (for example, Instant Replay)
✅ Standard customer-submitted recordings
If you don’t see a Network tab, the recording type likely doesn’t support network capture.
What gets captured
You can expect to see:
Fetch/XHR requests
Page navigations and redirects
Static assets (JS, CSS, images, fonts)
Third-party requests (analytics, CDNs)
WebSocket connections (when present)
Per request, you typically get URL, method, status, timing, and a waterfall. You may also see headers, payload, and response data.
Where to find it
Open the recording
Open the recording or capture in Screendesk.
Open the Network tab
Click Network in the developer tools panel.
Filter to what matters
Start with XHR/Fetch. Then enable Errors only if needed.
How to use network logs (fast workflow)
Find the failing request
Look for 4xx, 5xx, or Failed.
Inspect details
Check Headers, then Payload, then Response.
Copy and reproduce
Use Copy as cURL to reproduce outside the browser.
Common status codes and what to do
0 / Failed
Usually CORS, blocked requests, timeouts, or a dropped connection.
Check console logs for CORS errors. Check system info for VPN/network hints.
401 Unauthorized
Token missing or expired. Session issues are common.
Ask the user to log out/in. Check auth refresh logic.
403 Forbidden
Auth is present. Permission is not.
Check roles, entitlements, and feature flags.
404 Not Found
Bad URL or missing resource.
Check routing, environment (staging vs prod), and ID validity.
5xx Server error
Usually an engineering escalation.
Include URL, payload, response body, and timestamp in the ticket.
Privacy and security
Network logs can include sensitive data. Treat them like production logs.
Be careful with auth headers, cookies, and PII in payloads/responses.
Recommended practices:
Restrict access to technical roles.
Redact tokens before sharing externally.
Avoid screenshots of raw headers/payloads.
Limitations
Large request bodies may be truncated.
File uploads can show as
[Binary Data].Some third-party requests may omit bodies due to browser restrictions.
Static assets can appear, but the full body might not be stored.
Related pages
Last updated
Was this helpful?