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/capture-browser-trace.md
+26-26Lines changed: 26 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,39 +26,39 @@ Google Chrome and Microsoft Edge (Chromium) are both based on the [Chromium open
26
26
27
27
1. In the portal, navigate to the step just prior to where the issue occurs.
28
28
29
-
1. Press F12 or select  > **More tools** > **Developer tools**.
29
+
1. Press F12 or select  > **More tools** > **Developer tools**.
30
30
31
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
32
33
33
1. Select the **Network** tab, then select **Preserve log**.
34
34
35
-
35
+
36
36
37
37
1. Select the **Console** tab, select **Console settings**, then select **Preserve Log**. Select **Console settings** again to close the settings pane.
38
38
39
-
39
+
40
40
41
41
1. Select the **Network** tab, then select **Stop recording network log** and **Clear**.
42
42
43
-
43
+
44
44
45
45
1. Select **Record network log**, then reproduce the issue in the portal.
46
46
47
-
47
+
48
48
49
49
You will see session output similar to the following image.
50
50
51
-
51
+
52
52
53
53
1. After you have reproduced the unexpected portal behavior, select **Stop recording network log**, then select **Export HAR** and save the file.
54
54
55
-
55
+
56
56
57
57
1. Stop Steps Recorder, and save the file.
58
58
59
59
1. Back in the browser developer tools pane, select the **Console** tab. Right-click, then select **Save as...**, and save the console output to a text file.
60
60
61
-
61
+
62
62
63
63
1. Package the HAR file, console output, and screen recording in a compressed format like .zip, and share that with Microsoft support.
64
64
@@ -72,39 +72,39 @@ The following steps show how to use the developer tools in Microsoft Edge (EdgeH
72
72
73
73
1. In the portal, navigate to the step just prior to where the issue occurs.
74
74
75
-
1. Press F12 or select  > **More tools** > **Developer tools**.
75
+
1. Press F12 or select  > **More tools** > **Developer tools**.
76
76
77
77
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:
78
78
79
79
1. Select the **Network** tab, then clear the option **Clear entries on navigate**.
80
80
81
-
81
+
82
82
83
83
1. Select the **Console** tab, then select **Preserve Log**.
84
84
85
-
85
+
86
86
87
87
1. Select the **Network** tab, then select **Stop profiling session** and **Clear session**.
88
88
89
-
89
+
90
90
91
91
1. Select **Start profiling session**, then reproduce the issue in the portal.
92
92
93
-
93
+
94
94
95
95
You will see session output similar to the following image.
96
96
97
-
97
+
98
98
99
99
1. After you have reproduced the unexpected portal behavior, select **Stop profiling session**, then select **Export as HAR** and save the file.
100
100
101
-
101
+
102
102
103
103
1. Stop Steps Recorder, and save the file.
104
104
105
105
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. Right-click, then select **Copy**, and save the console output to a text file.
106
106
107
-
107
+
108
108
109
109
1. Package the HAR file, console output, and screen recording in a compressed format like .zip, and share that with Microsoft support.
110
110
@@ -116,49 +116,49 @@ The following steps show how to use the developer tools in Apple Safari. For mor
116
116
117
117
1. Select **Safari**, then select **Preferences**.
118
118
119
-
119
+
120
120
121
121
1. Select the **Advanced** tab, then select **Show Develop menu in menu bar**.
122
122
123
-
123
+
124
124
125
125
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.
126
126
127
-
1. Start recording the steps you take in the portal. For more information, see [How to record the screen on your Mac](https://support.apple.comHT208721).
127
+
1. Start recording the steps you take in the portal. For more information, see [How to record the screen on your Mac](https://support.apple.com/HT208721).
128
128
129
129
1. In the portal, navigate to the step just prior to where the issue occurs.
130
130
131
131
1. Select **Develop**, then select **Show Web Inspector**.
132
132
133
-
133
+
134
134
135
135
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:
136
136
137
137
1. Select the **Network** tab, then select **Preserve Log**.
138
138
139
-
139
+
140
140
141
141
1. Select the **Console** tab, then select **Preserve Log**.
142
142
143
-
143
+
144
144
145
145
1. Select the **Network** tab, then select **Clear Network Items**.
146
146
147
-
147
+
148
148
149
149
1. Reproduce the issue in the portal. You will see session output similar to the following image.
150
150
151
-
151
+
152
152
153
153
1. After you have reproduced the unexpected portal behavior, select **Export** and save the file.
154
154
155
-
155
+
156
156
157
157
1. Stop the screen recorder, and save the file.
158
158
159
159
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. Use Command-C to copy the output and save it to a text file.
160
160
161
-
161
+
162
162
163
163
1. Package the HAR file, console output, and screen recording in a compressed format like .zip, and share that with Microsoft support.
0 commit comments