Generating a HAR log file for Support

Issue

Automox Support has requested a HAR file to troubleshoot a problem in the Automox console — for example, a page that fails to load, a report or dashboard that times out, a sign-in or SSO error, or an action in the UI that returns an error. Instructions are needed for capturing the HAR file in the browser being used.

Environment

• Automox console (console.automox.com)
• Desktop browsers: Google Chrome, Microsoft Edge, Mozilla Firefox (Windows, macOS, Linux); Apple Safari (macOS)

Overview

A HAR (HTTP Archive) file is a JSON-formatted record of every network request and response the browser makes while the capture is running — including URLs, status codes, headers, and timing. It lets Support see exactly which console or API request is failing or slow, which is often impossible to determine from a screenshot alone.

Two rules apply in every browser:

• Start the capture before reproducing the problem. The browser only records traffic while the developer tools panel is open. If the error has already happened, reload the page or repeat the action with the panel open.
• Keep the log across page loads. Enable the browser's preserve/persist option so the recording survives redirects and navigation — important when capturing sign-in or SSO issues.

A HAR file can contain sensitive data, including cookies, session tokens, and any values typed into forms during the capture. Capture only the affected console session (not unrelated tabs), avoid entering unrelated credentials while recording, and attach the file directly to the support ticket rather than posting it anywhere public. See the Notes section for what Chrome removes automatically.

Resolution

Google Chrome and Microsoft Edge

Chrome and Edge share the same developer tools, so the steps are identical.

1. Open the affected console page in its own tab.
2. Open developer tools: press F12 (or Ctrl+Shift+I on Windows, Cmd+Option+I on macOS), or right-click the page and select Inspect.
   
3. Select the Network tab.
4. Select the Preserve log checkbox.
5. Confirm recording is active — the record button at the left of the Network toolbar is red. Click the clear button (⃠) to discard traffic captured so far.
6. Reproduce the problem (reload the page, retry the sign-in, or repeat the failing action).
7. Click the Export HAR button (downward-arrow icon) in the Network toolbar, name the file, and click Save.
   

Mozilla Firefox

1. Open the affected console page in its own tab.
2. Open the Network tool directly: press Ctrl+Shift+E (Windows/Linux) or Cmd+Option+E (macOS). (F12 followed by selecting the Network tab also works.)
3. Click the gear icon in the Network toolbar and select Persist Logs.
4. Reproduce the problem.
5. Click the gear icon again and select Save All As HAR, then save the file. (Right-clicking any request in the list and selecting Save All As HAR does the same thing.)
   

Apple Safari (macOS)

Safari's developer tools are hidden by default and must be enabled once:

1. Open Safari Settings (or Preferences on older versions), select the Advanced tab, and enable the web-developer features checkbox (labeled Show features for web developers on current versions).
2. Open the affected console page, then open the Web Inspector: press Cmd+Option+I, or choose Develop Show Web Inspector.
3. Select the Network tab.
4. Select the Preserve Log checkbox.
5. Reproduce the problem.
6. Click Export (upper-right of the Network tab) and save the file (Safari saves it with a .har extension).
   

Attach the file to the ticket

1. Verify the saved file has a .har extension.
2. Attach it to the existing Automox Support ticket (reply to the ticket email with the file attached, or upload it in the help center request). If the file exceeds the attachment size limit, compress it to .zip first.

Notes

• Timing matters. Note the approximate time (with time zone) the problem was reproduced and include it in the ticket — it helps Support correlate the HAR with server-side logs.
• Recent Chrome and Edge releases export a sanitized HAR by default, with cookies and authorization headers removed. The sanitized export is sufficient for most console troubleshooting; only provide the "with sensitive data" variant if Support specifically asks for it.
• Firefox and Safari do not sanitize HAR exports — the file includes cookies and headers as captured.
• Mobile browsers are not covered here; HAR capture requires a desktop browser, and the Automox console is designed for desktop use.
• If the problem spans multiple pages (for example, an SSO redirect loop), keep the same tab and developer-tools panel open for the whole flow — the preserve/persist setting from the steps above keeps the entire sequence in one file.