You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-portal/azure-portal-browser-trace.md
+61-13Lines changed: 61 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,46 +14,94 @@ manager: mtillman
14
14
15
15
# Capture a browser trace for troubleshooting
16
16
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.
18
18
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
20
20
21
21
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.
22
22
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
+
23
25
1. In the portal, navigate to the step just prior to where the issue occurs.
24
26
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:
- Safari: first enable the developer tools by selecting **Preferences** > **Advanced** > **Show Develop menu in menu bar**. Then select **Develop** > **Show Web Inspector**.
26
68
27
69
1. Select the **Network** tab.
28
70
29
71
1. To ensure that, select the appropriate option for your browser:
30
72
31
-
-For Edge, clear the option **Clear entries on navigate**.
73
+
- Edge: clear the option **Clear entries on navigate**.
32
74
33
-
-For Chrome, select **Preserve log**.
75
+
- Chrome: select **Preserve log**.
34
76
35
-
-For Safari, select ****.
77
+
- Safari: select ****.
36
78
37
79
1. Stop the browser trace session and clear the session.
38
80
39
-
-For Edge, select **Stop profiling session** and **Clear session**.
81
+
- Edge: select **Stop profiling session** and **Clear session**.
40
82
41
-
-For Chrome, select **Stop recording network log** and **Clear**.
83
+
- Chrome: select **Stop recording network log** and **Clear**.
42
84
43
-
-For Safari, select ****.
85
+
- Safari: select ****.
44
86
45
87
1. Restart the session, then reproduce the issue in the Azure portal. You will see session output similar to the following image.
46
88
47
89
1. Stop the session and save the trace as a HAR file.
48
90
49
-
-For Edge, select **Export as HAR**.
91
+
- Edge: select **Export as HAR**.
50
92
51
-
-For Chrome, select **Export HAR**.
93
+
- Chrome: select **Export HAR**.
52
94
53
-
-For Safari, select ****.
95
+
- Safari: select ****.
54
96
55
97
1. Compress the HAR file and send it to support for analysis and troubleshooting.
56
98
57
99
1. Console
58
100
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
0 commit comments