eG Monitoring
 

Measures reported by XMLogonStatsTest

Frequent login failures and inexplicable delays when accessing the XenMobile server can have an adverse impact on a user's experience with XenMobile. To capture such failures/delays proactively and isolate their root-cause, administrators can use the XMLogonStatsTest test.

At configured intervals, this test emulates a user logging into XenMobile. In the process, the test captures every step of the user login and reports the time taken at each step. This way, unusual slowness in logging in can be captured and where the login process was delayed can be determined - when connecting to XenMobile? Or when authenticating?

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
connStatus Indicates whether/not the user could connect to XenMobile.   The values that this measure reports and their corresponding numeric values are listed in the table below:

Measure Value Numeric Value
Success 1
Failed 0

Note:

By default, this measure reports the Measure Values discussed in the table above. However, in the graph of this measure, the status of the connection is indicated using the numeric equivalents only.
timeToConn Indicates the time taken to connect to XenMobile. Secs A low value is desired for this measure. A high value indicates a connection bottleneck.
authStatus Indicates whether/not the login credentials of the user were successfully authenticated.   The values that this measure reports and their corresponding numeric values are listed in the table below:

Measure Value Numeric Value
Success 1
Failed 0

Note:

By default, this measure reports the Measure Values discussed in the table above. However, in the graph of this measure, the status of the authentication is indicated using the numeric equivalents only.
tmeToAuth Indicates the time taken to authenticate the user login. Secs A high value for this measure could indicate an authentication delay.
timeToLogin Indicates the total time taken to login to XenMobile. Secs A high value indicates a login delay. In this case, you can compare the value of the timeToConn and tmeToAuth measures to know where the login was bottlenecked.