Overview

In some troubleshooting cases, the Elevar Support team may request console logs or a browser trace in addition to, or instead of, a HAR file. Follow this guide to learn how to collect console logs and browser traces.

Console Logs

Understanding Console Logs:

Console logs capture browser-level errors and warnings that occur when scripts run on your site.

How to Save Console Logs:

• Navigate to the page where the issue occurs.
• Right-click anywhere on the page and choose Inspect (or press Cmd + Option + I on Mac / Ctrl + Shift + I on Windows).
• Open the Console tab and reproduce the issue.
• Right-click inside the console window:
  • In Chrome or Edge, click Save As...
  • In Firefox, click Save All Messages to File
  • In Safari, click Save Selected
• When done, save the file (for example, console_logs.txt).

Browser Traces

Understanding Browser Traces:

Browser traces (available in Chrome) capture a deeper record of your browser’s internal actions during a session, which is helpful for diagnosing redirect loops, performance issues, or unusual script behavior.

Record a Browser Trace (Chrome Only):

• In Chrome, open a new tab and open the following website: https://yourdomain.com/cdn-cgi/trace
• Replace yourdomain.com with your website’s domain.
• The page will load a block of diagnostic data, then copy the full text output.
• Paste this content directly into your Elevar Support ticket or save it as a .txt file.

📘

NOTE: When to Send Console Logs or Traces

Include these files with your support ticket if you’re seeing:

• JavaScript errors or warnings in the browser console.
• Unresponsive pixels or scripts on specific pages.
• Slow page performance or script timeouts.
• Checkout redirects or unexpected page reloads.

Providing these logs alongside a HAR file gives our Support team full visibility into both network and browser-side activity, helping us diagnose issues more quickly.