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