How to record browser bugs with console logs and network errors

What console logs add to a bug report

Console output can include application messages, warnings, and errors. Look for messages that appear when the visible failure occurs, and preserve their wording and time. An error mentioning a missing value or failed operation may point to the part of the page that needs investigation.

A console error alone does not establish the cause. Some warnings are unrelated to the problem. Describe the action you took and connect the relevant message to the moment it appeared in the recording.

Which network request details matter?

• Method and URL: identify the operation the page attempted.
• Status: indicate whether the server returned success or an error.
• Timing: show whether the request coincided with a delay or the visible failure.
• Request and response data: may explain an unexpected value or a server error when that data is available in the capture.

For example, a failed save action followed by a 500 response is useful evidence of a server failure, but the developer still needs to investigate the underlying cause. A successful response can also accompany an incorrect result, so do not filter your report down to error statuses alone.

Capture the issue and its browser context

1. Install Bugxy, sign in, and connect Google Drive using desktop Chrome.
2. Open the affected page and prepare the starting conditions.
3. Start the recording before performing the action that triggers the bug.
4. Reproduce the issue, leaving the failed result visible long enough to understand.
5. Stop and wait for the upload, then inspect the recording and captured console and network information.

Capture availability depends on the page, browser permissions, and recording settings. Start a new recording if important actions happened before capture began. Do not assume a report contains every request or message from the browser.

Connect the evidence to the visible failure

Note where the failure occurs in the video, what you clicked immediately before it, and which message or request appears at that time. Include the expected result separately from the actual result.

For a checkout problem, the report might say: “After Apply coupon, the total increases. The checkout request returns an unexpected amount.” The recording, relevant response, and reproduction steps provide a more useful starting point than a screenshot of the final total.

Check captured data before sharing

Request URLs, payloads, console messages, and screen recordings can contain sensitive information. Bugxy redacts common authentication fields, but review the captured context yourself and use test accounts and data when possible.

The video is stored in your connected Google Drive; Bugxy stores the report metadata and captured technical context. Review the report and sharing permissions before distributing its link.