|
Measures reported by AWSEc2VmConnTest
Sometimes, an instance could be in a powered-on state, but the failure of the operating system or any fatal error in internal operations of the instance could have rendered the instance inaccessible to users. In order to enable you to promptly detect such 'hidden' anomalies, this test periodically runs a connectivity check on each instance available for the configured AWS user account in the monitored region, and reports whether the instances are accessible over the network or not.
The measures
made by this test are as
follows:
| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Avg_delay |
Indicates the average delay between transmission of packets to this instance and receipt of the response to the packet at the source. |
Secs |
An increase in network latency could result from misconfiguration of the router(s) along the path, network congestion, retransmissions at the network, etc. |
| Min_delay |
The minimum time between transmission of a packet and receipt of the response back. |
Secs |
A significant increase in the minimum round-trip time is often a sure sign of network congestion. |
| Pkt_loss_pct |
Indicates the percentage of packets lost during transmission from source to target and back. |
Percent |
Packet loss is often caused by network buffer overflows at a network router or by packet corruptions over the network. The detailed diagnosis for this measure provides a listing of routers that are on the path from the external agent to target server, and the delays on each hop. This information can be used to diagnose the hop(s) that could be causing excessive packet loss/delays. |
| Availability |
Indicates whether the network connection to this instance is available or not. |
Percent |
A value of 100 indicates that the instance is accessible over the network. The value 0 indicates that the instance is inaccessible.
Typically, the value 100 corresponds to a Packet loss of 0.
|
|