eG Monitoring
 

Measures reported by SPOLoginTest

SharePoint Online is a cloud-based service that helps organizations share and collaborate with colleagues, partners, and customers. Where SharePoint Online is used, users need to be able to quickly and easily login to SharePoint Online, so that they have on-demand access to internal sites, documents, and other information. If users are unable to login to SharePoint Online when in need, their productivity is bound to get badly hit. Frequent logon issues may also force users to question the reliability of this cloud-based service. To ensure ‘happy users’, administrators should promptly capture logon issues, isolate its root cause, and rapidly initiate measures to address it. This is where the SPOLoginTest test helps!

This test emulates a user logging into SharePoint Online via the Office 365 REST API. The emulated logon process is as outlined below:

  1. The eG agent uses the Office 365 login credentials configured for the eG tests to login to the REST API.

  2. Once Azure AD successfully validates the credentials, the authentication step completes.

  3. After successful authentication, the eG agent hits the SharePoint URL of the monitored Office 365 domain to complete the login.

The test reports the success/failure of each step of the emulated logon process. Additionally, the test also measures the time taken to complete every step. This way, the test enables administrators to proactively detect problems in a typical user logon to SharePoint Online and also pinpoints the exact step of the logon process where the bottleneck lies - in authentication? or when the domain-specific URL is hit?

Outputs of the test : One set of results for the SharePoint server on the cloud.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Authentication_status Indicates whether/not the login credentials were validated by Azure AD.   If the login credentials are successfully validated by Azure AD, then this measure will report the value Success. The value Failed is reported if authentication fails.

The numeric values that correspond to these measure values are as follows:

Measure Value Numeric Value
Success 1
Failed 0

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the login status. In the graph of this measure however, the same is indicated using the numeric equivalents only.
Authentication_time Indicates the time taken for the login credentials to be validated. Seconds An abnormally high value is a cause cor concern, as it indicates that authentication is slow.

If you suspect issues in the API logon process, then compare the value of this measure with that of the Login time measure to know where exactly the logon process is bottlenecked - is it during authentication - i.e., when login credentials are validated by Azure AD? or is it at login - i.e., when the domain-specific URL is hit?
Login_status Indicates the percentage of packets lost during transmission from source to server and back.   If this measure reports the value Success, it means that the test was able to connect to the SharePoint URL of the domain, successfully. On the other hand, if this measure reports the value Failed, it implies that the test could not connect to the SharePoint URL of the domain.

The numeric values that correspond to these measure values are as follows:

Measure Value Numeric Value
Success 1
Failed 0

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the login status. In the graph of this measure however, the same is indicated using the numeric equivalents only.
Login_time Indicates the time taken to connect to the SharePoint URL of the monitored domain. Seconds An abnormally high value is a cause cor concern, as it indicates that it is taking an unusually long time to connect to the SharePoint URL.

If the Total_login_time reports an abnormally high value, then compare the value of this measure with that of the Authentication_time measure to know where exactly the logon process is bottlenecked - is it at authentication - i.e., when login credentials are validated by Azure AD? or is it at login - i.e., when the domain-specific URL is hit?
Total_login_time Indicates the total time taken to complete the API logon process. Seconds A very high value for this measure indicates a bottleneck in the API logon process. Under such circumstances, compare the value of the Authentication time and Login time measures to know what is delaying API logon - authentication? or connecting to the SharePoint URL?