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
+16-8Lines changed: 16 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,9 +14,11 @@ 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, 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 browser you use: Microsoft Edge (EdgeHTML), Microsoft Edge (Chromium), Google Chrome, or Apple Safari.
18
18
19
-
## Microsoft Edge
19
+
## Microsoft Edge (EdgeHTML)
20
+
21
+
The following steps show how to use the developer tools in Microsoft Edge (EdgeHTML). For more information, see [Microsoft Edge (EdgeHTML) Developer Tools](/microsoft-edge/devtools-guide).
20
22
21
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.
22
24
@@ -26,7 +28,7 @@ If you're troubleshooting an issue with the Azure portal, and you need to contac
26
28
27
29
1. Press F12 or select  > **More tools** > **Developer tools**.
28
30
29
-
1.Ensure that the trace captures information from all the pages you visit in the portal:
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:
30
32
31
33
1. Select the **Network** tab, then clear the option **Clear entries on navigate**.
32
34
@@ -40,19 +42,25 @@ If you're troubleshooting an issue with the Azure portal, and you need to contac
40
42
41
43

42
44
43
-
1. Restart the session, then reproduce the issue in the portal. You will see session output similar to the following image.
45
+
1. Select **Start profiling session**, then reproduce the issue in the portal.
46
+
47
+

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

46
52
47
-
1.Stop the session, then select **Export as HAR** and save the file.
53
+
1.After you have reproduced the unexpected portal behavior, select **Stop profiling session**, then select **Export as HAR** and save the file.
48
54
49
-

55
+

50
56
51
57
1. Stop Steps Recorder, and save the file.
52
58
53
-
1. Select the **Console** tab, expand the window, and take screenshots of the output.
59
+
1. 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. Copy the output and save it to a text file.
60
+
61
+

54
62
55
-
1. Package the HAR file, console screenshot, and Steps Recorder in a compressed format like .zip, and share that with Microsoft support.
63
+
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