Network Traffic - OS Test
This test monitors the incoming and outgoing traffic through each virtual desktop on the cloud.
Target of the test : An Amazon Cloud Desktop Group
Agent deploying the test : A remote agent
Outputs of the test : One set of results for every virtual_desktop:network_interface combination
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The nick name of the Amazon Cloud Desktop Group component for which this test is to be configured. |
Port |
Refers to the port at which the specified host listens to. By default, this is NULL. |
Inside View Using |
To obtain the 'inside view' of performance of the desktops - i.e., to measure the internal performance of the cloud-based virtual desktops - this test uses a light-weight eG VM Agent software deployed on each of the desktops. Accordingly, this parameter is by default set to eG VM Agent. |
Report Powered OS |
If this flag is set to Yes (which is the default setting), then the 'inside view' tests will report measures for even those desktops that do not have any users logged in currently. Such desktops will be identified by their name and not by the username_on_desktopname. On the other hand, if this flag is set to No, then this test will not report measures for those desktops to which no users are logged in currently. |
Report By User |
This flag is set to Yes by default. The value of this flag cannot be changed. This implies that the cloud-based virtual desktops in environments will always be identified using the login name of the user. In other words, in cloud environments, this test will, by default, report measures for every username_on_desktopname. |
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. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Incoming traffic |
Indicates the rate at which data (including framing characters) is received on a network interface. |
Mbps |
An abnormally high rate of incoming traffic may require additional analysis. |
Outgoing traffic |
Represents the rate at which data (including framing characters) is sent on a network interface. |
Mbps |
An abnormally high rate of outgoing traffic may require additional analysis. |
Maximum bandwidth |
An estimate of the capacity of a network interface. |
Mbps |
|
Bandwidth usage |
Indicates the percentage of bandwidth used by a 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) |
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 could not be transmitted 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. |
Note:
If the Network Traffic - OS test is not reporting measures for a desktop, make sure that you have enabled the SNMP service for the desktop.