Support teams often ask for "browser logs" when a customer reports a broken page. That request is too vague.

A HAR file and a console log answer different questions. Asking for the wrong one wastes time and can create unnecessary data risk.

When to Ask for a HAR File

Ask for a HAR file when the issue depends on network behavior.

Good HAR use cases:

  • Login or SSO failures.
  • Redirect loops.
  • API requests returning 400, 401, 403, 404, or 500.
  • Slow page loads.
  • Missing images, scripts, or assets.
  • CORS errors.
  • Tenant-specific responses.
  • Browser-only behavior that server logs do not explain.

A HAR file helps answer:

  • Which request failed?
  • What status code came back?
  • Did the request hit the expected endpoint?
  • Did the browser redirect?
  • Did the request happen before or after login?
  • How long did each request take?

When to Ask for Console Logs

Ask for console logs when the issue likely involves client-side code or visible application behavior.

Good console-log use cases:

  • Blank screens.
  • JavaScript errors.
  • UI actions that do nothing.
  • Extension conflicts.
  • Warnings from third-party scripts.
  • Feature flags or runtime configuration issues.
  • Errors shown only after the page loads.

Console logs help answer:

  • Did JavaScript throw an error?
  • Did a warning point to a blocked resource?
  • Did the app log a specific failure reason?
  • Did the failure happen before or after a user action?

When to Ask for Both

Ask for both when the browser flow and client-side behavior are connected.

Common examples:

  • Login succeeds but the app shows a blank page.
  • An API request fails and the UI shows a generic error.
  • The page loads, then breaks after a user clicks a button.
  • The app works for one tenant but not another.
  • Support needs to map a console error to the failed network request.

For these cases, ask the customer to capture both artifacts from the same reproduction attempt, with a timestamp and steps.

When a Screenshot Is Enough

Sometimes a screenshot is the safer and faster request.

Use a screenshot when:

  • The issue is visual.
  • An error message is visible.
  • The support team already has server logs.
  • The workflow contains highly sensitive data.
  • The customer cannot safely collect logs.

Do not ask for HAR files or console logs by reflex. Ask for the minimum evidence needed.

Copyable Support Request

Could you capture browser troubleshooting evidence for this issue?

Please include:
1. A screenshot of the visible error.
2. A HAR file if the page makes a network request during the failure.
3. Console logs if the page shows a JavaScript error or blank screen.
4. The timestamp, timezone, browser version, and exact reproduction steps.

Please review or sanitize files before sharing and upload them through the secure link in this ticket.

Evidence Decision Rule

Use this quick rule:

  • Network request failed: ask for a HAR.
  • JavaScript error appeared: ask for console logs.
  • User saw something unexpected: ask for a screenshot.
  • Login or redirect broke: ask for HAR plus timestamp.
  • Blank screen after loading: ask for HAR, console log, and screenshot.

FAQ

Is a HAR file the same as a console log?

No. A HAR file records network requests and responses. Console logs record browser-side messages, warnings, and JavaScript errors.

Can console logs contain sensitive data?

Yes. Console logs can include tokens, user data, error details, IDs, URLs, and debug output. Review them before sharing.

Can a HAR file show JavaScript errors?

Usually no. A HAR can show failed requests that may cause a JavaScript error, but the console log shows the client-side error itself.

Should support ask customers for both every time?

No. Ask for both only when both network and browser-side behavior matter.

CTA

Redaction Retriever helps teams review HAR files, console logs, screenshots, and reproduction notes locally before packaging support evidence.