![]() ![]() My favorite feature is the Geo Map, which provides the globe map. All of them have links that will bring interactive dashboards. The “your environment” section is the summary of all objects, including Azure regions, virtual networks, VPN gateways, Network Security Groups, and subnet. We also have a small section called “do more,” where we have a link to the log search (log analytics) and the documentation. The traffic visualization section provides a graphical view of the network traffic flow distribution (in Item 1, we can choose between bytes and flows). The initial page has several sections, as follows: The initial page has a top bar where we need to select the log analytics that is being used by the Traffic Analytics (we defined that in the NSG flows) and the interval. Use Azure Policies to enforce/enable settings.Define the diagnostic log settings during the ARM template deployment process.Use scripting (PowerShell or Azure CLI) after the fact.If you think that the process is tedious using Azure Portal, you have several options to manage diagnostic logs, here are a few options available: We can have more than one diagnostic log entry per resource. Keep in mind that diagnostic logs can send log information to event hubs, storage or log analytics. We can check all possible settings available even before you try to add a diagnostic setting (Item 3).We can set a new diagnostic setting entry (Item 2).We can see any existing diagnostic settings already configured for this resource (Item 1).Here is a summary of what is available on this simple page: ![]() At first, it seems like a simple and annoying page that requires an additional click, but there are some subtle details on it. When we click on any of the resources that we want to enable diagnostics, a new blade will be displayed. Note: If you use Azure Monitor to configure diagnostic settings, you have the same interface, but the difference is that Network Watcher lists all network-related resources in a single location. We can narrow down by resource group and resource type. The other component of this area is Diagnostics Logs, and it will list all network components on the selected subscription. For the Traffic Analytics, we need to determine the frequency (1 hour or 10 minutes) and the Log Analytics that is going to be used. Version 2 adds bytes and packet to the mix.įor the flows, we need to define the retention in a number of days and storage account. Both versions log egress IP traffic for both types of traffic, which are allowed or denied. In the new blade, we can enable the flow logs and select which version. We can see at a glance all the Network Security Groups and their current configuration without the need to check individual properties. Click on the desired NSG.Īn NSG can have flows (status column) being configured and also Traffic Analytics status (Traffic Analytics status column). Click on NSG flow logs item on the left side, and a list of Network Security Groups will be listed. To enable Traffic Analytics, we need to start by enabling NSG flow logs. The tool shows the VMs, their IP addresses, Next Hop, the numbers of a probe sent and failed, as well as topology view. The response of this tool is fantastic, and it provides a lot of information that will help the cloud administrator identify the root cause of the connectivity issue. An agent extension is required, and it will be installed as part of the process. In the connection troubleshoot item, we can pick and choose two VMs in our Azure for source and target. After that just click on the Start Troubleshooting button. When using VPN troubleshoot, the cloud administrator needs to select a Storage Account and a container and then select one or more network gateways. When troubleshooting hybrid cloud, the virtual network gateway component is vital to understand what is going on between Azure and on-premises. We are going to complete the series by checking on Traffic Analytics, which is a great feature to have in your Azure environment. In this second of our two-part series on Network Watcher, we are going to cover some features that we didn’t have the chance to write about in the first article. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |