Statistics

Stat Show

Stat Show dumps all of the HCL Traveler statistics to the Domino® Console. It then provides the percentage of prime syncs and device syncs that were successful, including the average time syncs are taking. The following is an example summary included with the results of a Stat Show command:

There are 12 users registered on this server.
  8 percent (1) of the users have been offline for more than 24 hours.
  92 percent (11) of the users are online or have been within the past 24 hours.
    There are 11 mailfiles currently being monitored for these online users.

There are 25 devices registered on this server.
    64 percent (16) of the devices are registered for HTTP notifications.
    36 percent (9) of the devices are registered for Exchange ActiveSync notifications.
    16 percent (4) of the devices have been offline for more than 24 hours.
    84 percent (21) of the devices are online or have been within the past 24 hours.
    4 percent (1) of the devices are currently connected to the server via HTTP.
    28 percent (7) of the devices are currently connected to the server via Exchange ActiveSync.
    36 percent (9) of the devices are using the Apple client for Apple iOS.
    40 percent (10) of the devices are using the Traveler client for Apple iOS.
    16 percent (4) of the devices are using the Traveler client for Android.
    8 percent (2) of the devices are using HCL Traveler for Microsoft Outlook (HTMO).
There have been 3,279 prime syncs.
  The average prime sync took 686 ms.
  99 percent (3,278) of the prime syncs were successful.
    The average successful prime sync took 685 ms.
  1 percent (1) of the prime syncs failed.
    The average failed prime sync took 5,042 ms.
    1 percent (1) of the prime syncs ended in result 500.
      The average 500 prime sync took 5,042 ms.
There are an average of 0.007 prime syncs running at any given time.

There have been 6,603 device syncs.
  The average device sync took 1,722 ms and transferred 30,506 bytes.
  99 percent (6,589) of the device syncs were successful.
    The average successful device sync took 571 ms.
  1 percent (14) of the device syncs failed.
    The average failed device sync took 543,317 ms.
    1 percent (10) of the device syncs ended in result 408.
      The average 408 device sync took 633,304 ms.
    1 percent (4) of the device syncs ended in result 409.
      The average 409 device sync took 318,349 ms.
There are an average of 0.034 device syncs occurring at any given time.

The following list highlights the sync return codes:

• 200=Successful
• 408=Request Timeout (the device did not respond before the server timed out the session)
• 409=Conflict (the device started a new session that caused this session to be aborted)
• 500=Unknown Error
• 503=Server Busy

Included in the statistics are histogram statistics for both device syncs (device to server requests) and prime syncs (server to mail file).

DeviceSync.Time.Histogram.200.000-001 = 5871
   DeviceSync.Time.Histogram.200.001-002 = 453
   DeviceSync.Time.Histogram.200.002-005 = 128
   DeviceSync.Time.Histogram.200.005-010 = 116
   DeviceSync.Time.Histogram.200.010-030 = 17
   DeviceSync.Time.Histogram.200.030-060 = 3
   DeviceSync.Time.Histogram.200.120-Inf = 1
   DeviceSync.Time.Histogram.408.120-Inf = 9
   DeviceSync.Time.Histogram.409.010-030 = 2
   DeviceSync.Time.Histogram.409.120-Inf = 2
...
   PrimeSync.Time.Histogram.200.000-001 = 2940
   PrimeSync.Time.Histogram.200.001-002 = 16
   PrimeSync.Time.Histogram.200.002-005 = 32
   PrimeSync.Time.Histogram.200.005-010 = 284
   PrimeSync.Time.Histogram.200.010-030 = 5
   PrimeSync.Time.Histogram.200.060-120 = 1
   PrimeSync.Time.Histogram.200.120-Inf = 1
   PrimeSync.Time.Histogram.500.005-010 = 1

The histogram statistics are the number of seconds in each range for a given return code. For example, PrimeSync.Time.Histogram.200.000-001 = 2940 indicates that there were 2940 prime synchronizations with a 200 (Successful) return code between 0 and 1 seconds. This continues up to PrimeSync.Time.Histogram.200.120-Inf = 1, which indicates that 1 prime synchronization with a 200 return code took more than 120 seconds.

Histograms are useful statistics for seeing whether syncs are taking too long, the system is overloaded, or there is a lot of network delay in the environment. If the system is running slow, the histogram statistics tend toward the larger numbers. The prime sync histogram numbers are the best to check to see how the system is performing overall. The prime synchronizations are not dependent on the carrier network delay or the device speed.

For more information on what the individual statistics mean, see System stat results.