Windows Network Traffic - AVD Test

This is an internal test that monitors the incoming and outgoing traffic through the chosen Session Host/Azure Virtual Desktop.

Target of the test : An Azure Virtual Desktop

Agent deploying the test : An internal agent.

Outputs of the test : One set of results for each network interface on the chosen Session Host / Azure Virtual Desktop

Configurable parameters for the test
Parameters	Description
Test Period	How often should the test be executed.
Host	The host for which the test is to be configured.
Port	The default port is NULL.
Exclude	If you want to exclude specific network interfaces from monitoring, then provide a comma-separated list of interface names / name patterns that should not be monitored, in the Exclude text box. Wild card characters can be used to indicate patterns - for eg., to ignore all network interfaces with names that end with '_2', your specification can be: *_2. By default, all interfaces with names that begin with VMware_Virtual_Ethernet_Adapter are excluded from monitoring. You can change this default setting if you need.
Is Full Duplex	By default, this flag is set to Yes, indicating that the incoming and outgoing data traffic is handled in full duplex mode. This means that the network interfaces are sending and receiving data at the same time. If the data traffic in your environment is handled in half-duplex mode, set this flag to No. This means that the network interfaces are not sending and receiving data at the same time; in essence, it is a one-way conversation. In this case, the test halves the value of the Incoming traffic and Outgoing traffic measures.
Report by Connection DD	By default, this flag is set to No. This implies that by default, the network interfaces are identified using their names. On the other hand, if you want the test to identify the network interfaces using their connection IDs instead of the names, then set this flag to Yes. Then, the test will identify the network interfaces using the connection IDs and report metrics for every connection ID.
Show Top	This parameter is applicable only when the Trace flag is set to Yes and the Detailed Diagnosis flag is set to On. By default, the detailed diagnosis of this test lists the top-10 processes/applications on the virtual desktop, in terms of the network traffic they generate. If you want detailed diagnosis to display more or less number of top applications, then change the value of this parameter.
Trace	By default, the Trace flag is set to No. This indicates that the test does not report any detailed diagnostics by default. However, if unusually high network traffic is flowing into the Azure virtual desktop , then you may want to know which application/process on the desktop is the destination for this traffic. For deep-dive insights into the incoming network traffic of the target virtual desktop, you need to enable the detailed diagnosis capability of the test. For this, set the Trace flag to Yes. Note: This test will report detailed metrics only if the Trace flag is set to Yes and the Detailed Diagnosis flag is set to On. If either or both these flags are turned off, then the test will not report detailed statistics.
Event Capture Interval In Secs	This parameter is applicable only when the Trace flag is set to Yes and the Detailed Diagnosis flag is set to On. By default, the value of this parameter is set to 10 seconds. This setting ensures that the detailed diagnosis of the test will capture the incoming/outgoing network traffic observed during the last 10 seconds of a measurement period. However, you can override the default value of this parameter as per your requirement.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Incoming traffic	Indicates the rate at which data (including framing characters) is received on this network interface.	Mbps	An abnormally high rate of incoming traffic may require additional analysis. In such a situation, use the detailed diagnosis of this measure to identify the process/application that is receiving the maximum traffic. Note: Detailed diagnostics will be available only if the Trace flag and the Detailed Diagnosis flag of this test are enabled.
Outgoing traffic	Represents the rate at which data (including framing characters) is sent on this network interface.	Mbps	An abnormally high rate of outgoing traffic may require additional analysis. In such a situation, use the detailed diagnosis of the Outgoing traffic measure to identify the process/application that is sending the maximum traffic. Note: Detailed diagnostics will be available only if the Trace flag and the Detailed Diagnosis flag of this test are enabled.
Maximum bandwidth	An estimate of the capacity of this network interface.	Mbps
Bandwidth usage	Indicates the percentage of bandwidth used by this network interface.	Percent	By comparing the bandwidth usage with the maximum bandwidth of an interface, an administrator can determine times when the network interface is overloaded or is being a performance bottleneck.
Output queue length	Indicates the length of the output packet queue (in packets) on this interface.	Number	If this is longer than 2, delays are being experienced and the bottleneck should be found and eliminated if possible.
Outbound packet errors	The number of outbound packets that this interface could not transmit because of errors.	Number	Ideally, number of outbound errors should be 0.
Inbound packet errors	The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.	Number	Ideally, number of inbound errors should be 0.