eG Help

If there is something that can mar user experience with SharePoint Online, then it is the frequent unavailability and consistently poor responsiveness of the sites hosted on SharePoint Online. This is why, administrators prioritize site accessibility-related issues above all else, and strive to capture and fix such issues before users notice and complain. This is where the SPOSiteConnectivityTest test comes in handy!

For each site that is configured for monitoring, this test, at frequent intervals, emulates an HTTP/S connection to that site and reports on the availability and responsiveness of that site. Besides sending out pre-emptive alerts to administrators regarding the unavailability/slowness of a site, the test also reports the response code returned by the site for the emulated request. In the event that the site is unavailable, the response code will point administrators to the probable reason for the non-availability. Also, a web site can be considered truly ‘available’, only if the page that is hit displays ‘valid’ content - i.e., the content that it is supposed to display during normal operations, and not junk data or error messages. The SPOSiteConnectivityTest test also reports the validity of the content of the target site, and thus paints a ‘true’ picture of availability.

First-level descriptor: Display Name of a site, in the SITE URL configuration

Measurement	Description	Measurement Unit	Interpretation
Web_availability	This measurement indicates whether this site was able to respond successfully to the query made by the test.	Number	If this measure reports the value 100%, it implies that the site is accessible. The value 0 on the other hand indicates that the site is nopt accessible over HTTP/S. Availability failures could be caused by several factors such as the web site being down, the web site being misconfigured, a network failure, etc. Temporary unavailability may also occur if the web site is overloaded. Availability is determined based on the response code returned by the site. A response code between 200 to 300 indicates that the site is available.
Content_validity	This measure validates whether this site was successful in executing the request made to it.	Percent	A value of 100% indicates that the content returned by the test is valid. A value of 0% indicates that the content may not be valid. This capability for content validation is especially important for multi-tier web applications. For example, a user may not be able to login to the web site but the site may reply back with a valid HTML page where in the error message, say, “Invalid Login” is reported. In this case, the availability will be 100 % (since we got a valid HTML response). If the test is configured such that the content parameter should include the string “About Us”, in the above scenario content validity would have a value 0.
Response_code	The response code returned by this site for the simulated request	Number	A value between 200 and 300 indicates a good response. A 4xx value indicates a problem with the requested content (eg., page not found). A 5xx value indicates a server error.
Response_time	This measurement indicates the time taken by this site to respond to the requests it receives.	Seconds	Response time being high denotes a problem. Poor response times may be due to the site being overloaded or misconfigured. If the URL accessed involves the generation of dynamic content, backend problems (e.g., an overload at the application server or a database failure) can also result in an increase in response time.