SaaS TCP Connectivity Test

If your Microsoft Yammer users complain of inaccessibility, you may want to check the quality of the network link (TCP connection) to the Microsoft Yammer. A flaky or latent TCP network connection to the Microsoft Yammer can sometimes deny access to the users, thus, adversely impacting their overall experience with Microsoft Yammer. To avoid this, periodically run the SaaS TCP Connectivity test, and check the health of the TCP connections to the Microsoft Yammer.

This is an external test that emulates a TCP connection to the Microsoft Yammer and reports the count of connections that were successful and the count of connections that failed. In addition, this test also throws light on how responsive the Microsoft Yammer is to TCP connection requests. In the process, the test reveals any break or slowness in the network connection to the Microsoft Yammer service.

Target of the test : Microsoft Yammer

Agent deploying the test : An external agent

Outputs of the test : One set of results for each SITE URL:Port monitored

First-level descriptor: SITE URL:Port

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. By default, this is portal.office.com

URLs

By default, www.yammer.com:443 will be specified against this parameter. However, you can provide a comma-separated list of sites to be monitored.The format of your specification should be as follows: <Site_URL>:<Port>. For example, your specification can be:

www.yammer.com:443,portal.office.com:443

Note that the <Site_URL> specifications will be the descriptors of this test.

Packets to be Sent

The number of packets to be transmitted during the test
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Successful connections

Indicates the number of TCP connections that were successful for this site.

Number

 

Failed connections

Indicates the number of TCP connections that failed for this site.

Number

A high value for this measure indicates a flaky/latent network connection.

Percent of failed connections

Indicates the percentage of connections that failed for this site.

Percent

Ideally, the value of this measure should be close to 0%.

Maximum latency

Indicates the maximum time taken by this site to respond to TCP connection requests that it receives.

Milliseconds

An increase in the value of these measures is a cause for concern. Given below are some common reasons for such an anomaly:

  • The network between the site and the eG external agent is congested. When there is an increase in traffic on the interconnecting network, data transmission can slow down, thereby increasing communication latency.

  • The quality of the network connection between the eG external agent and the site is sub-par. Poor signal quality, faulty transmission lines, etc. can result in an increase in packet loss and/or network latency.

  • The site is overloaded. If the site is very busy, it takes longer to respond to requests, and this will result in an increase in latency.

  • There are problems with network routingbetween the site and the eG external agent. A faulty network router, routing loops, etc., can increase network latency. Check the detailed diagnosis of this test to track latency on the first three hops between the agent and the site. The latency to each hop can be used to determine which hop the problem lies in.

Minimum latency

Indicates the minimum time taken by this site to respond to TCP connection requests that it receives.

Milliseconds

Average latency

Indicates the average time taken by this site to respond to TCP connection requests that it receives.

Milliseconds