Skip to content

Commit 4f0d677

Browse files
committed
Add browser sections
1 parent 86dab82 commit 4f0d677

File tree

1 file changed

+61
-13
lines changed

1 file changed

+61
-13
lines changed

articles/azure-portal/azure-portal-browser-trace.md

Lines changed: 61 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -14,46 +14,94 @@ manager: mtillman
1414

1515
# Capture a browser trace for troubleshooting
1616

17-
If you're troubleshooting an issue with the Azure portal, and you need to contact Microsoft support, we recommend you first capture a browser trace and some additional information. The browser trace can provide important details about the network traffic at the time the issue occurs.
17+
If you're troubleshooting an issue with the Azure portal, and you need to contact Microsoft support, we recommend you first capture a browser trace and some additional information. The information you collect can provide important details about the portal at the time the issue occurs. Follow the steps in this article for the brower you use: Microsoft Edge, Google Chrome, or Apple Safari.
1818

19-
Follow the steps in this article to capture a trace and export a _HAR file_ with the trace information. We show the steps in the Microsoft Edge, Google Chrome, and Apple Safari browsers.
19+
## Microsoft Edge
2020

2121
1. Sign in to the [Azure portal](https://portal.azure.com). It's important to sign in _before_ you start the trace so that the trace doesn't contain sensitive information related to your sign-in.
2222

23+
1. Start recording the steps you take in the portal, using [Steps Recorder](https://support.microsoft.com/help/22878/windows-10-record-steps).
24+
2325
1. In the portal, navigate to the step just prior to where the issue occurs.
2426

25-
1. Press F12 to open the developer tools pane, or open it from a tools menu (More tools > Developer tools).
27+
1. Press F12 or select **More Tools** > **Developer Tools**.
28+
29+
1. Ensure that the trace captures information from all the pages you visit in the portal:
30+
31+
1. Select the **Network** tab, and clear the option **Clear entries on navigate**.
32+
33+
1. Select the **Console** tab, and select **SOMELOGTHING**.
34+
35+
1. Select the **Network** tab.
36+
37+
1. Select **Stop profiling session** and **Clear session**.
38+
39+
1. Restart the session, then reproduce the issue in the portal. You will see session output similar to the following image.
40+
41+
1. Stop the session and select **Export as HAR**.
42+
43+
1. Compress the HAR file and send it to support for analysis and troubleshooting.
44+
45+
1. Select the **Console** tab
46+
47+
1. Copy and save
48+
49+
50+
## Scratch
51+
52+
1. Sign in to the [Azure portal](https://portal.azure.com). It's important to sign in _before_ you start the trace so that the trace doesn't contain sensitive information related to your sign-in.
53+
54+
1. (Optional) Start recording the steps you take in the portal, using [Steps Recorder](https://support.microsoft.com/help/22878/windows-10-record-steps).
55+
56+
1. In the portal, navigate to the step just prior to where the issue occurs.
57+
58+
Ive also seen some teammates ask customer to collect a problem recorder trace which screen grabs their monitor when they click through some repro, so this might be also good to reference or include into workflow, whatever you guys recommend:
59+
60+
61+
1. Open the developer tools pane:
62+
63+
- Edge: select **More Tools** > **Developer Tools**.
64+
65+
- Chrome: select **More tools** > **Developer tools**.
66+
67+
- Safari: first enable the developer tools by selecting **Preferences** > **Advanced** > **Show Develop menu in menu bar**. Then select **Develop** > **Show Web Inspector**.
2668

2769
1. Select the **Network** tab.
2870

2971
1. To ensure that, select the appropriate option for your browser:
3072

31-
- For Edge, clear the option **Clear entries on navigate**.
73+
- Edge: clear the option **Clear entries on navigate**.
3274

33-
- For Chrome, select **Preserve log**.
75+
- Chrome: select **Preserve log**.
3476

35-
- For Safari, select ****.
77+
- Safari: select ****.
3678

3779
1. Stop the browser trace session and clear the session.
3880

39-
- For Edge, select **Stop profiling session** and **Clear session**.
81+
- Edge: select **Stop profiling session** and **Clear session**.
4082

41-
- For Chrome, select **Stop recording network log** and **Clear**.
83+
- Chrome: select **Stop recording network log** and **Clear**.
4284

43-
- For Safari, select ****.
85+
- Safari: select ****.
4486

4587
1. Restart the session, then reproduce the issue in the Azure portal. You will see session output similar to the following image.
4688

4789
1. Stop the session and save the trace as a HAR file.
4890

49-
- For Edge, select **Export as HAR**.
91+
- Edge: select **Export as HAR**.
5092

51-
- For Chrome, select **Export HAR**.
93+
- Chrome: select **Export HAR**.
5294

53-
- For Safari, select ****.
95+
- Safari: select ****.
5496

5597
1. Compress the HAR file and send it to support for analysis and troubleshooting.
5698

5799
1. Console
58100

59-
1. I’ve also seen some teammates ask customer to collect a problem recorder trace which screen grabs their monitor when they click through some repro, so this might be also good to reference or include into workflow, whatever you guys recommend: https://support.microsoft.com/en-us/help/22878/windows-10-record-steps
101+
1.
102+
103+
## Google Chrome
104+
105+
## Apple Safari
106+
107+
## Next steps

0 commit comments

Comments
 (0)