AR System MidTier - SaaS/OnPrem - How to capture network traffic using F12 (Developer Tools) when Fiddler is not an option
Knowledge Article
AR System MidTier - SaaS/OnPrem - How to capture network traffic using F12 (Developer Tools) when Fiddler is not an option
Remedy - AR System MidTier - How to capture network traffic using F12 (Developer Tools) when Fiddler is not an option
Remedy AR System Server
AR System Mid Tier
AR System MidTier
Remedy AR System Server
AR System Mid Tier
AR System MidTier
If you need to capture the HTTP traffic between a browser and a web server we usually go for Fiddler. However what can you do when Fiddler is not an option?
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers.
Modern web browsers include debugging tools that allow you to examine the page. They also allow you to capture the network traffic similar to Fiddler. Here's how you do this:
Most browsers have a limitation as the network capture would only work on the current window. Any new tab or window would not start capturing network traffic when opened. The only browser that has improved this condition is Chrome so far.
Firefox
Open Firebug via the F12 keyboard shortcut.
Select the Network tab.
Select the Disable cache and Persist logs options (right side of panel).
Reproduce the problem.
Right click on one of the recorded requests, select Save All as HAR.
Save the file and send it to BMC Support.
Safari:
In Safari, go to the webpage in question.
Enable Developers Tool: Safari > Preferences > Advance > Click Show Develop menu in menu bar.
Select Develop in menu > Show Web Inspector > Select Network tab.
Within the Networks tab, select Preserve log option.
Refresh the page and allow Safari to record the browser-website interaction.
Once the page is loaded, click on Export on the top right in the window of the Network tab.
Select the Console tab and screen capture the errors.
Upload the HAR and console screenshot files to the support ticket.
Chrome:
Open F12 Dev Console via the F12 keyboard shortcut.
Select the Network tab.
Select the Preserve Log and Disable cache options.
Reproduce the problem.
When done, right click on one of the recorded requests and choose: Save All as HAR with content.
Save the file (you don't need to select the sessions, it will save all the session currently displayed).
Provide the HAR file to BMC Support.
Edge:
Press F12 to open the debug pane.
Clear the session history before reproducing.
To clear the session history press the button indicated by three lines and a red "X".
Press the play button at the top left of the debug pane to start recording.
Reproduce the issue.
Press the red square to stop recording.
Export the results as a HAR file by pressing the save button that is identified as a floppy disk
Details on how to gather HAR files for Microsoft Edge can be found in their help documentation
If new windows or tabs would be opened to replicate this scenario then before starting turn on "Auto-open DevTools for popups": Press F12, Click on the gear icon on the F12 toolbar, on the Preference section, bottom far right turn on :