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
description: Provides guidance about using the Network Logs (NetLog) tool as an alternative to Fiddler and HTTP Archive (HAR) captures.
4
4
ms.reviewer: bachoang, v-weizhu
5
-
ms.date: 04/08/2025
5
+
ms.date: 04/11/2025
6
6
ms.service: entra-id
7
7
ms.topic: how-to
8
8
ms.custom: sap:Enterprise Applications
9
9
---
10
10
# Use NetLog as an alternative to Fiddler and HAR captures
11
11
12
-
This article provides guidance on using the Network Logs (NetLog) tool as an alternative to Fiddler and HTTP Archive (HAR) captures for diagnosing network issues in Microsoft Entra. NetLog is built into in Chromium-based browsers like Microsoft Edge, Chrome, and Electron. When standard Fiddler captures are unavailable or HAR captures from developer tools truncate necessary information, you can use it to capture network activity.
12
+
This article provides guidance on using the Network Logs (NetLog) tool as an alternative to Fiddler and HTTP Archive (HAR) captures to diagnose network issues in Microsoft Entra. NetLog is built into Chromium-based browsers like Microsoft Edge, Google Chrome, and Electron. When standard Fiddler captures are unavailable or HAR captures from developer tools truncate necessary information, you can use NetLog to capture network activity.
13
13
14
14
## Known limitations
15
15
16
16
Before using NetLog, be aware of the following limitations:
17
17
18
18
- POST request bodies aren't captured.
19
-
- Sites running in compatibility mode for Internet Explorer aren't captured.
19
+
- Sites running in Internet Explorer compatibility mode aren't captured.
20
20
21
21
Depending on the information you need, you might still need to use Fiddler or HAR captures.
22
22
@@ -26,28 +26,30 @@ Follow these steps to capture network activity using NetLog:
26
26
27
27
1. (Optional but helpful) Close all browser tabs except one.
28
28
1. Navigate to NetLog:
29
-
- For Chrome: Open a new tab and go to `chrome://net-export`.
29
+
- For Google Chrome: Open a new tab and go to `chrome://net-export`.
30
30
- For Microsoft Edge: Open a new tab and go to `edge://net-export`.
31
31
1. In the **Options** section, select **Include raw bytes (will include cookies and credentials)**.
32
32
1. Leave the **Maximum log size** field blank.
33
33
1. Select **Start Logging to Disk**.
34
-
1. Select a location (such as **Desktop**) to save the log file (*edge-net-export-log.json* or *chrome-net-export-log.json*).
35
-
1.Within the same browser window, open a new tab.
34
+
1. Select a location (such as **Desktop**) to save the log file (**edge-net-export-log.json** or **chrome-net-export-log.json**).
35
+
1.In the same browser window, open a new tab.
36
36
1. Reproduce the issue.
37
37
38
38
> [!NOTE]
39
39
> If you close or navigate away from the NetLog tab, the logging will stop automatically.
40
40
1. After reproducing the issue, return to the NetLog tab and select the **Stop Logging** button.
41
41
1. Locate the NetLog file saved in step 6.
42
42
43
+
For more information, see [How to capture a NetLog dump](https://dev.chromium.org/for-testers/providing-network-details).
44
+
43
45
## Use NetLog on mobile devices
44
46
45
-
NetLog is supported on mobile versions of Edge and Chrome:
47
+
NetLog is supported on mobile versions of Microsoft Edge and Google Chrome:
46
48
47
-
- Android: NetLog works in Edge and Chrome for Android.
48
-
- iOS: NetLog works in Chrome for iOS.
49
+
- Android: NetLog works in Edge and Google Chrome for Android.
50
+
- iOS: NetLog works in Google Chrome for iOS.
49
51
50
-
On mobile devices, you will have an email option to send the log.
52
+
On mobile devices, you have an email option to send the log.
51
53
52
54
## View and analyze NetLog data
53
55
@@ -58,10 +60,10 @@ You can use the following tabs in the NetLog Viewer to inspect different aspects
58
60
-**Events**: View detailed network events.
59
61
-**Proxy**: Check proxy settings.
60
62
-**Timeline**: Analyze request timing.
61
-
-**DNS**: Inspect DNS lookups.
62
-
-**Sockets**: Review TCP connections.
63
+
-**DNS**: Inspect Domain Name System (DNS) lookups.
64
+
-**Sockets**: Review Transmission Control Protocol (TCP) connections.
63
65
-**Cache**: Examine cached resources.
64
66
65
-
For more information, see [Providing network details with NetLog](https://dev.chromium.org/for-testers/providing-network-details).
67
+
[!INCLUDE [Third-party information disclaimer](../../../includes/third-party-disclaimer.md)]
66
68
67
69
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
0 commit comments