Review Collected Logs from Zight Video Requests

Zight Support
Zight Support
  • Updated

Overview

Zight video requests can collect browser and app logs alongside a customer recording. When logs are collected, Zight shows a dedicated logs viewer next to the video player so support, QA, and engineering teams can review what happened on screen and inspect the related technical details in one place.

Use this workflow when a written description is not enough to reproduce an issue, when a customer is seeing browser errors, or when your team needs cleaner context before escalating a bug.

Before you begin

  • Create a request from the Zight desktop app, Chrome extension, web dashboard, or a supported integration.
  • Turn on Collect logs before you send the request.
  • Ask the recipient to complete the request as they normally would.
Create Request Link dialog in Zight with Video selected
Create a video request from Zight.
Ask to collect logs toggle enabled in the Zight request link settings
Enable Collect logs before sharing the request.

Review collected logs

  1. Open the submitted video reply in Zight.
  2. Use the video player to review the visual context of the issue.
  3. Open the logs viewer next to the video player.
  4. Switch between log sections such as Console, Network, and Errors.
  5. Compare log timestamps and error details with what is happening in the video.
  6. Download the collected logs when you need to attach the full record to another tool or share it with engineering.
  7. Use the ticket or bug action when you need to create a follow-up item with the relevant context.
Zight logs viewer showing Console log entries next to a video reply
Review console and browser activity beside the video reply.
Zight logs viewer showing Errors tab with script errors
Use the Errors tab to spot failures that may explain the issue.

What you can inspect

  • Console: browser console output and logged events.
  • Network: request activity that may help identify failed calls or timing issues.
  • Errors: captured script errors and other failures that can help narrow the root cause.
  • Browser details: useful environment context for reproducing or escalating the issue.

Tips and best practices

  • Ask for logs when the issue is technical, intermittent, or hard to reproduce.
  • Review the video first, then use the logs viewer to confirm what happened behind the scenes.
  • Capture the exact moment where the issue appears in the video and compare it with nearby log entries.
  • Download logs before escalating if the engineering team needs a complete copy.
  • Add a short summary of what you found when creating a ticket so the next person has context.

Troubleshooting

  • I do not see logs next to the video: confirm that Collect logs was enabled before the request was sent.
  • The reply only shows a video: the recipient may have completed a request that did not ask for logs, or logs may not have been available for that session.
  • The logs are noisy: start with the Errors tab, then check Console and Network entries around the same timestamp.
  • I need to share this with engineering: download the logs and include the Zight reply link, a short issue summary, and the timestamp where the issue appears.

Related articles

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.