Troubleshooting
Capture Browser Logs
Collect console and network logs for HeartLab support troubleshooting.
Capture Browser Logs
If you're experiencing issues while using HeartLab in your web browser, HeartLab Support may request:
- Console logs
- Network logs (HAR files)
These logs help diagnose browser, network, and application issues more effectively.
The instructions in this guide are based on the latest browser versions available at the time of writing. Depending on your browser version or operating system, some steps or menu names may vary slightly.
What to Send
Please provide both:
- Console logs
- Browser warnings and errors
- Network HAR file
- Browser request and response activity
Good Capture Practice
For the most useful troubleshooting information:
- Open developer tools before reproducing the issue.
- Enable Preserve log where available.
- Clear existing logs before testing.
- Reproduce the issue once.
- Export logs immediately after reproduction.
- Attach exported files to your support ticket.
Windows
Microsoft Edge
Capture Console Logs
- Open Microsoft Edge.
- Select the three-dot menu in the top-right corner.
- Navigate to:
- More tools → Developer Tools
- Open the Console tab.
- Select the gear icon and enable:
- Preserve log
- Ensure:
- All levels is selected
- Clear existing logs:
CTRL + L
- Reproduce the issue.
- Right-click within the console and select:
- Save as
Capture Network Logs
- Open the Network tab.
- Reproduce the issue.
- If possible, identify failed requests (commonly shown in red, e.g. HTTP 422).
- Select:
- Save all as HAR with content
- Compress the HAR file into a
.zipfile if required before sending.
Google Chrome
Capture Console Logs
- Open Chrome.
- Open Developer Tools:
Ctrl + Shift + I- or
F12
- Open the Console tab.
- Reproduce the issue.
- Right-click inside the console and select:
- Save as
Capture Network Logs
- Open Developer Tools.
- Navigate to the Network tab.
- Enable:
- Preserve log
- Select:
- Clear
- Reproduce the issue.
- Select:
- Export HAR
Mozilla Firefox
Capture Console Logs
- Open Firefox.
- Navigate to:
- Menu → Web Developer → Web Console
- or press
Ctrl + Shift + K
- Reproduce the issue.
- Right-click within the console and select:
- Save Page As
Capture Network Logs
- Navigate to:
- Menu → Web Developer → Network
- or press
Ctrl + Shift + E
- Reproduce the issue.
- Right-click within the request list and select:
- Save All As HAR
macOS
Safari
Capture Console and Network Logs
- Open Safari.
- Navigate to:
- Safari → Preferences → Advanced
- Enable:
- Show Develop menu in menu bar
- or Show features for web developers
- Close Preferences.
- Open the affected HeartLab page.
- Select:
- Develop → Show JavaScript Console
- Open the Network tab.
- Leave the console open and reproduce the issue.
- Right-click any request and select:
- Export as HAR
- Save the file.
Google Chrome (macOS)
Capture Console Logs
- Open Chrome.
- Open Developer Tools:
Option + ⌘ + J
- Open the Console tab.
- Reproduce the issue.
- Right-click inside the console and select:
- Save as
Capture Network Logs
- Open Developer Tools.
- Navigate to the Network tab.
- Enable:
- Preserve log
- Select:
- Clear
- Reproduce the issue.
- Select:
- Export HAR
Mozilla Firefox (macOS)
Capture Console Logs
- Open Firefox.
- Navigate to:
- Menu → More Tools → Web Developer Tools
- Open the Console tab.
- Reproduce the issue.
- Right-click within the console and select:
- Save All Messages to File
Capture Network Logs
- Open Web Developer Tools.
- Navigate to the Network tab.
- Reproduce the issue.
- Right-click within the request list and select:
- Save All As HAR
Include These Details in Your Support Ticket
When submitting logs to HeartLab Support, include:
- Approximate time the issue occurred
- Username or affected user role
- URL or page where the issue occurred
- Steps performed before the issue appeared
- Screenshot of any visible error message (if available)
Additional Notes
Browser logs may contain technical request information. Review organisational policies before sharing logs externally.
Capturing logs immediately after reproducing the issue provides the most accurate troubleshooting information.
Remember to reproduce the issue only after opening the Console and Network tabs. Capturing logs before reproduction may omit important troubleshooting information.