Troubleshoot Fing Web App: Capture and Submit a Browser Trace

Capturing details for investigations

The Fing Web App provides access to the network data available in your Fing account. If you encounter a problem, for example, a data mismatch  between the Web App and your Mobile App, or blank and empty pages, or crashes reported in the Browser console log, please report the issue to the Fing Support Team at support@fing.com.

When you submit problem details,  provide a HAR file that most of the major browsers allow  to record for investigations. Please follow the instructions for the browser you experience the issue with. It's advisable to include also a screenshot or screen recording of the issue, to provide a proper context and to help replicate the issue.

Microsoft Edge

The following steps show how to use the developer tools in Microsoft Edge. For more information, see Microsoft Edge DevTools.

• Right mouse click on the browser page and select Inspect. You can also launch the tools from the toolbar menu under More tools > Developer tools.
• By default, the browser keeps trace information only for the page that's currently loaded. Set the following options so the browser keeps all trace information, even if your repro steps require going to more than one page.
• Select the Console tab, select Console settings, then select Preserve Log.

• Select the Network tab. If that tab isn't visible, click the More tools (+) button and select Network. Then, from the Network tab, select Preserve log.

• On the Network tab, select Stop recording network log and Clear.

• Select Record network log, then reproduce the issue in the Fing Web App.

You'll see session output similar to the following image.

• After you have reproduced the issue in the Web App , select Stop recording network log, then select Export HAR and save the file.

• Back in the browser developer tools pane, select the Console tab. Right-click one of the messages, then select Save as..., and save the console output to a text file.

• Package the browser trace HAR file, console output, and screen recording files in a compressed format such as .zip.
• Share the compressed file in your request.

Google Chrome

The following steps show how to use the developer tools in Google Chrome. For more information, see ChromeDevTools.

• Right mouse click on the browser page and select Inspect. You can also launch the tools from the toolbar menu under More tools > Developer tools.
• By default, the browser keeps trace information only for the page that's currently loaded. Set the following options so the browser keeps all trace information, even if your repro steps require going to more than one page.
• Select the Console tab, select Console settings, then select Preserve Log.

• Select the Network tab, then select Preserve log.

• On the Network tab, select Stop recording network log and Clear.

• Select Record network log, then reproduce the issue in the Fing Web App.

You'll see session output similar to the following image.

• After you have reproduced the issue on Fing Web App , select Stop recording network log, then select Export HAR and save the file.

• Back in the browser developer tools pane, select the Console tab. Right-click one of the messages, then select Save as..., and save the console output to a text file.

• Package the browser trace HAR file, console output, and screen recording files in a compressed format such as .zip.

• Share the compressed file in your request

Safari

The following steps show how to use the developer tools in Apple Safari on Mac. For more information, see SafariDevTools.

• Select Safari, then select Preferences
• Select the Advanced tab, then select Show Develop menu in menu bar.

• Select Develop, then select Show Web Inspector.

• By default, the browser keeps trace information only for the page that's currently loaded. Set the following options so the browser keeps all trace information, even if your repro steps require going to more than one page.
• Select the Console tab, then select Preserve Log.

• Select the Network tab, then select Preserve Log.

• On the Network tab, select Clear Network Items.

• Reproduce the issue in the Fing Web App You'll see session output similar to the following image.

  

• After you have reproduced the issue on Fing Web App , select Export and save the file.

• Back in the browser developer tools pane, select the Console tab, and expand the window. Place your cursor at the start of the console output then drag and select the entire contents of the output. Use Command-C to copy the output and save it to a text file.

• Package the browser trace HAR file, console output, and screen recording files in a compressed format such as .zip.

• Share the compressed file in your request

Firefox

The following steps show how to use the developer tools in Firefox. For more information, see FireFox DevTools.

• Right mouse click on the browser page and select Inspect. You can also launch the tools from the toolbar menu under More tools > Developer tools.
• By default, the browser keeps trace information only for the page that's currently loaded. Set the following options so the browser keeps all trace information, even if your repro steps require going to more than one page.
• Select the Console tab, select the Settings icon, and then select Persist Logs.

• Select the Network tab, select the Settings icon, and then select Persist Logs.

• On the Network tab, select Clear.

• Reproduce the issue in the Fing Web App. You'll see session output similar to the following image

• After you have reproduced the issue on Fing Web App, select Save All As HAR.

• Back in the browser developer tools pane, select the Console tab. Right-click one of the messages, then select Save All Messages to File, and save the console output to a text file.

• Package the browser trace HAR file, console output, and screen recording files in a compressed format such as .zip.

• Share the compressed file in your request

How to submit a request to investigate the issue

• Click the Submit Request link.
• Attach the .zip saved locally and a video/screenshot of the issue  in the Attachment section by clicking on the Add file button.
• Provide as much detail as possible about the issue (conditions, steps to reproduce) and the network affected.
• In the subject enter 'Web App crash/error'
• Click on Submit.