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
+47-5Lines changed: 47 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,53 @@ 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 information you collect can provide important details about the portal at the time the issue occurs. Follow the steps in this article for the browser you use: Microsoft Edge (EdgeHTML), Microsoft Edge (Chromium), Google Chrome, or Apple Safari.
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 developer tools in the browser you use: Google Chrome or Microsoft Edge (Chromium), Microsoft Edge (EdgeHTML), or Apple Safari.
18
+
19
+
## Google Chrome and Microsoft Edge (Chromium)
20
+
21
+
Google Chrome and Microsoft Edge (Chromium) are both based on the [Chromium open source project](https://www.chromium.org/Home). The following steps show how to use the developer tools, which are very similar in the two browsers. For more information, see [Chrome DevTools](https://developers.google.com/web/tools/chrome-devtools) and [Microsoft Edge (Chromium) Developer Tools](/microsoft-edge/devtools-guide-chromium).
22
+
23
+
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.
24
+
25
+
1. Start recording the steps you take in the portal, using [Steps Recorder](https://support.microsoft.com/help/22878/windows-10-record-steps).
26
+
27
+
1. In the portal, navigate to the step just prior to where the issue occurs.
28
+
29
+
1. Press F12 or select  > **More tools** > **Developer tools**.
30
+
31
+
1. 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 requires going to more than one page:
32
+
33
+
1. Select the **Network** tab, then select **Preserve log**.
34
+
35
+

36
+
37
+
1. Select the **Console** tab, select **Console settings**, then select **Preserve Log**.
38
+
39
+

40
+
41
+
1. Select the **Network** tab, then select **Stop recording network log** and **Clear**.
42
+
43
+

44
+
45
+
1. Select **Record network log**, then reproduce the issue in the portal.
46
+
47
+

48
+
49
+
You will see session output similar to the following image.
50
+
51
+

52
+
53
+
1. After you have reproduced the unexpected portal behavior, select **Stop recording network log**, then select **Export HAR** and save the file.
54
+
55
+

56
+
57
+
1. Stop Steps Recorder, and save the file.
58
+
59
+
1. Back in the browser developer tools pane, select the **Console** tab. Select **Save as...**, and save the console output to a text file.
60
+
61
+

62
+
63
+
1. Package the HAR file, console output, and Steps Recorder in a compressed format like .zip, and share that with Microsoft support.
18
64
19
65
## Microsoft Edge (EdgeHTML)
20
66
@@ -62,10 +108,6 @@ The following steps show how to use the developer tools in Microsoft Edge (EdgeH
62
108
63
109
1. Package the HAR file, console output, and Steps Recorder in a compressed format like .zip, and share that with Microsoft support.
0 commit comments