System stat results

AddressCache.Count

Number of entries in the Traveler lookup address cache.

AddressCache.Hit.<type>

Number of times a lookup matched the cache by type (Canonical or Internet).

AddressCache.Missed.<type>

Number of times a lookup did not find a match in the cache by type (Canonical or Internet).

Availability.Index.<bucket>

A histogram stat with buckets. This stat discussed in Load balancing considerations.

Availability.Index is only applicable to HA configurations.

ConnectionManager.Count.<action>

The current number of connections open for that type of action.

ConnectionManager.Peak.<action>.Count

The peak (as opposed to the current) number of connections open for that type of action.

ConnectionManager.Peak.<action>.Time

The time that ConnectionManager.Peak.<action>.Count was hit/achieved/happened.

CPU.Pct.<bucket>

Traveler checks the CPU usage on a periodic basis. This stat is a histogram showing how many times the CPU percentage was in the specified range or bucket. The bucket values are "000-010", "010-020", "020-030", "030-040", "040-050", "050-060", "060-070", "070-080", "080-090", "090-100".

As an example, CPU.Pct.040-050 would show the number of times the CPU usage was between 40% and 50%.

ClusterCache.Access

How many times a ntsclcache database was accessed.

ClusterCache.Flush

How many times a ntsclcache database entry was deleted.

Constrained.Reason.<reason>

- Number of times the server entered a constrained state by reason (ex: DBConnectionWait).

Constrained.state

Whether or not Traveler is currently in the constrained state.

Constrained.count

The number of times Traveler entered the constrained state.

Constrained.Histogram.<bucket>

Histogram of the time spent (in seconds) in the constrained state. Buckets are "000-001", "001-002", "002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".

DB.Connections

The total number of connections currently allocated.

DB.Connections.Idle

The number of currently allocated connections available for new work.

DB.Connections.Max

The maximum number of connections that could be allocated.

DB.Connections.Peak

Time at which the DB.Connections stat hit the max.

DCA.C.CheckAccessRights

The number of times the access rights were checked for a database using the Domino® C API call.

DCA.C.Count.NSFDbClose

The number of times a database was closed using the Domino® C API call.

DCA.C.Count.NSFDbOpen

The number of times a database was opened using the Domino® C API call.

DCA.C.Count.NSFNoteClose

The number of times a note was closed using the Domino® C API call.

DCA.C.Count.NSFNoteOpen

The number of times a note was opened using the Domino® C API call.

DCA.C.DB_OPEN.Time.Histogram.<server>.<bucket>

Histogram of the time spent (in seconds) to open a database on the given server using the Domino® C API call. Server is the name of the Domino® server on which the database was opened. Buckets are "000-001", "001-002", "002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".

DCA.C.HTMLCreateConverter

The number of times an HTML Converter object was created.

This stat and DCA.C.HTMLDestroyConverter should generally match up if the system is idle.

DCA.C.HTMLDestroyConverter

The number of times an HTML converter object was destroyed.

This stat and DCA.C.HTMLCreateConverter should generally match up if the system is idle.

DCA.C.ModDoc.RunCount

Count of the number of times IBM Traveler had to determine which documents were changed.

DCA.C.ModDoc.SkippedDocs

The number of documents that IBM Traveler is ignoring because the document is not one of the documents that are syncable to device (i.e. hidden view, etc.)

DCA.C.ModDoc.SyncableDocs

The number of documents that can be synced to the device.

DCA.C.ModDoc.Time

The amount of time used to determine the syncable documents.

DCA.C.ModDocCountinue.RunCount

The number of times when the syncable document was greater than notes.ini parameter of NTS_PS_MAX_RETURN_DOCS (Default value is 100 documents).

DCA.C.NAMELookup

The number of times directory lookup is performed.

DCA.C.NAMELookup2

The number of times directory lookup is performed.

DCA.C.NSFDbGetNoteInfo

The number of times a document is access via the GetNoteInfo call.

DCA.ChangeDelayCount.<bucket>

The amount of time (in seconds) between when the document was last modified and when Traveler has detected the change during the prime sync. Buckets are "000-003", "003-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".

DCA.DB_CLOSE

The number of times a database was closed using the Domino® Java™ API.

DCA.DB_OPEN

The number of times a database was opened using the Domino® Java™ API.

DCA.DB_OPEN.Time.Histogram.<server>.<bucket>

Histogram of the time spent (in seconds) to open a database on the given server using the Domino® Java™ API call. Server is the name of the Domino® server on which the database was opened. Buckets are "000-001", "001-002", "002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".

DCA.DOCUMENT_CLOSE

The number of times a document was closed using the Domino® Java™ API.

DCA.DOCUMENT_OPEN

The number of times a document was opened using the Domino® Java™ API.

Database.Commit.Histogram.Successful.<bucket>

Histogram of the time spent (in seconds) to commit a transaction against Traveler's database. Buckets are "000-001", "001-002", "002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".

Database.Query.Histogram.<query>.<bucket>

Histogram of the time spent (in seconds) to execute the specified query against Traveler's database. Query is the query that was executed. Buckets are the same as Database.Commit.Histogram.Successful.

DelayQueue.DequeueDelayTime.<DelayQueue>.<bucket>

Histogram of the amount of time between a DelayQueueElement being dequeued from a DelayQueue and when it should have been dequeued. DelayQueue is the name of the DelayQueue. Buckets are "00-01", "01-10", "10-60", "60-Inf".

DeviceSync.Bytes.In.B

The total number of bytes received from devices during sync operations.

DeviceSync.Bytes.In.GB

The total number of gigabytes received from devices during sync operations. This is only present when the B becomes too large, so the real value is the combination of the two.

DeviceSync.Bytes.Out.B

The total number of bytes sent to devices during sync operations.

DeviceSync.Bytes.Out.GB

The total number of gigabytes sent to devices during sync operations. This is only present when the B becomes too large, so the real value is the combination of the two.

DeviceSync.Count.<SyncReturnCode>

The number of device syncs that had the specified return code. Most common return codes are: 200=OK, 408=Request Timeout (Device did not respond before the Server timed out the session), 409=Conflict (Device started a new session which caused this session to be aborted), 500=Unknown Error, 503=Server Busy

DeviceSync.Documents.ToDevice.Mail.Add

The total number of mail document adds sent from the server to a device.

DeviceSync.Documents.ToDevice.Mail.Delete

The total number of mail document deletes sent from the server to a device.

DeviceSync.Documents.ToDevice.Mail.Update

The total number of mail document updates sent from the server to a device.

DeviceSync.Documents.ToDevice.Calendar.Add

The total number of calendar event adds sent from the server to a device.

DeviceSync.Documents.ToDevice.Calendar.Delete

The total number of calendar event deletes sent from the server to a device.

DeviceSync.Documents.ToDevice.Calendar.Update

The total number of calendar event updates sent from the server to a device.

DeviceSync.Documents.ToDevice.Contacts.Add

The total number of contact adds sent server from the to a device.

DeviceSync.Documents.ToDevice.Contacts.Delete

The total number of contact deletes sent from the server to a device.

DeviceSync.Documents.ToDevice.Contacts.Update

The total number of contact updates sent from the server to a device.

DeviceSync.Documents.ToDevice.ToDo.Add

The total number of todo adds sent from the server to device.

DeviceSync.Documents.ToDevice.ToDo.Delete

The total number of todo deletes sent from the server to a device.

DeviceSync.Documents.ToDevice.ToDo.Update

The total number of todo updates sent from the server to a device.

DeviceSync.Documents.ToDevice.Journal.Add

The total number of journal document adds sent from the server to a device.

DeviceSync.Documents.ToDevice.Journal.Delete

The total number of journal document deletes sent from the server to a device.

DeviceSync.Documents.ToDevice.Journal.Update

The total number of journal document updates sent from the server to a device.

DeviceSync.Documents.ToDevice.Folder.Add

The total number of folder document adds sent from the server to a device.

DeviceSync.Documents.ToDevice.Folder.Delete

The total number of folder document deletes sent from the server to a device.

DeviceSync.Documents.ToDevice.Folder.Update

The total number of folder document updates sent from the server to a device.

DeviceSync.Documents.ToServer.Calendar.Add

The total number of calendar event adds sent from the device to a server.

DeviceSync.Documents.ToServer.Calendar.Delete

The total number of calendar event deletes sent from the device to a server.

DeviceSync.Documents.ToServer.Calendar.Update

The total number of calendar event updates sent from the device to a server.

DeviceSync.Documents.ToServer.Contacts.Add

The total number of contact adds sent from a device to the server.

DeviceSync.Documents.ToServer.Contacts.Delete

The total number of contact deletes sent from a device to the server.

DeviceSync.Documents.ToServer.Contacts.Update

The total number of contact updates sent from a device to the server.

DeviceSync.Documents.ToServer.Folder.Add

The total number of folder document adds sent from a device to the server.

DeviceSync.Documents.ToServer.Folder.Delete

The total number of folder document deletes sent from a device to the server.

DeviceSync.Documents.ToServer.Folder.Update

The total number of folder document updates sent from a device to the server.

DeviceSync.Documents.ToServer.Journal.Add

The total number of journal document adds sent from a device to the server.

DeviceSync.Documents.ToServer.Journal.Delete

The total number of journal document deletes sent from a device to the server.

DeviceSync.Documents.ToServer.Journal.Update

The total number of journal document updates sent from a device to the server.

DeviceSync.Documents.ToServer.Mail.Add

The total number of mail document adds sent from a device to the server.

DeviceSync.Documents.ToServer.Mail.Delete

The total number of mail document deletes sent from a device to the server.

DeviceSync.Documents.ToServer.Mail.Update

The total number of mail document updates sent from a device to the server.

DeviceSync.Documents.ToServer.ToDo.Add

The total number of todo adds sent from a device to the server.

DeviceSync.Documents.ToServer.ToDo.Delete

The total number of todo deletes sent from a device to the server.

DeviceSync.Documents.ToServer.ToDo.Update

The total number of todo updates sent from a device to the server.

DeviceSync.FetchCache.Add

The total number of times that records could not be added to the fetch cache because the cache was full.

DeviceSync.FetchCache.Oversize

The total number of times records were added to the fetch cache.

DeviceSync.FetchCache.Expired

The total number of times records expired out of the cache before they were fetched.

DeviceSync.FetchCache.Missing

The total number of times the fetch cache was searched for a record but records could not be found.

DeviceSync.InitialSyncUsers.Total

How many users have done an initial sync of any application.

DeviceSync.InitialSyncUsers.Calendar

How many users have done an Initial sync of the Calendar application.

DeviceSync.InitialSyncUsers.Contacts

How many users have done an Initial sync of the Contacts application.

DeviceSync.InitialSyncUsers.Folder

How many users have done an Initial sync of the Folder application.

DeviceSync.InitialSyncUsers.Journal

How many users have done an Initial sync of the Journal application.

DeviceSync.InitialSyncUsers.Mail.Inbox

How many users have done an Initial sync of the Mail application.

DeviceSync.InitialSyncUsers.ToDo

How many users have done an Initial sync of the To Do application.

DeviceSync.InitialSyncDevices.Total

The total number of Initial syncs for all applications done by devices.

DeviceSync.InitialSyncDevices.Calendar

How many devices have done an Initial sync of the Calendar application.

DeviceSync.InitialSyncDevices.Contacts

How many devices have done an Initial sync of the Contacts application.

DeviceSync.InitialSyncDevices.Folder

How many devices have done an Initial sync of the Folder application.

DeviceSync.InitialSyncDevices.Journal

How many devices have done an Initial sync of the Journal application.

DeviceSync.InitialSyncDevices.Mail.Inbox

How many devices have done an Initial sync of the Mail application.

DeviceSync.InitialSyncDevices.ToDo

How many devices have done an Initial sync of the To Do application.

DeviceSync.MismatchSyncUsers.Total

The total number of Mismatch syncs for all applications done by users.

DeviceSync.MismatchSyncUsers.Calendar

How many users have done an Mismatch sync of the Calendar application.

DeviceSync.MismatchSyncUsers.Contacts

How many users have done an Mismatch sync of the Contacts application.

DeviceSync.MismatchSyncUsers.Folder

How many users have done an Mismatch sync of the Folder application.

DeviceSync.MismatchSyncUsers.Journal

How many users have done an Mismatch sync of the Journal application.

DeviceSync.MismatchSyncUsers.Mail.Inbox

How many users have done an Mismatch sync of the Mail application.

DeviceSync.MismatchSyncUsers.ToDo

How many users have done an Mismatch sync of the To Do application.

DeviceSync.MismatchSyncDevices.Total

The total number of Mismatch syncs for all applications done by devices.

DeviceSync.MismatchSyncDevices.Calendar

How many devices have done an Mismatch sync of the Calendar application.

DeviceSync.MismatchSyncDevices.Contacts

How many devices have done an Mismatch sync of the Contacts application.

DeviceSync.MismatchSyncDevices.Folder

How many devices have done an Mismatch sync of the Folder application.

DeviceSync.MismatchSyncDevices.Journal

How many devices have done an Mismatch sync of the Journal application.

DeviceSync.MismatchSyncDevices.Mail.Inbox

How many devices have done an Mismatch sync of the Mail application.

DeviceSync.MismatchSyncDevices.ToDo

How many devices have done an Mismatch sync of the To Do application.

DeviceSync.Time.<SyncReturnCode>.Milliseconds

The amount of milliseconds that the server has spent (total) during device syncs. The most common return codes are: 200=OK, 408=Request Timeout (Device did not respond before the Server timed out the session), 409=Conflict (Device started a new session which caused this session to be aborted), 500=Unknown Error, 503=Server Busy.

DeviceSync.Time.<SyncReturnCode>.Days

The amount of days that the server has spent (total) during device syncs. This is only present when the Milliseconds becomes too large, so the real value is the combination of the two. The most common return codes are: 200=OK, 408=Request Timeout (Device did not respond before the Server timed out the session), 409=Conflict (Device started a new session which caused this session to be aborted), 500=Unknown Error, 503=Server Busy.

DeviceSync.Time.Histogram.<SyncReturnCode>.<bucket>

Histogram of the time spent (in seconds) to complete the device sync with the given sync return code. The most common return codes are: 200=OK, 408=Request Timeout (Device did not respond before the Server timed out the session), 409=Conflict (Device started a new session which caused this session to be aborted), 500=Unknown Error, 503=Server Busy Buckets are "000-001", "001-002", "002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".

Errors Errors.<user>

Number of errors logged (total).

ErrorType.<type>

Number of errors logged for the specified user.

GetAlarm.Time.Histogram.<bucket>

Number of errors logged for the specified type.

HADR.MonitorMoves

Number of times a user's master monitor has moved to another server in the pool. Monitor moves can occur because of load balancing or because of servers being restarted.

HADRMonitorMovesFrom.<server name>

Number of master monitor moves from the specified server.

HADRMonitorMovesTo.<server name>

Number of master monitor moves to the specified server.

HTTP.Headers.Response.X-IBM-TRAVELER-ERROR-MESSAGE.<message>

Count by error message being returned to device requests.

HTTP.Status.<error code>

Count by HTTP response code (200, 503, etc).

InterServer.Communications.Failure.<target>.<server id>

Number of times an inter-server communication has failed to the target (server or servlet) server id (server uid + hostname).

InterServer.Communication.Success.<target>.<server id>

- Number of times an inter-server communication to the server or servlet at the specified server (server unid + hostname) has succeeded.

IPC.DelayTime.<bucket>

Histogram of the time spent (in seconds) to get an Alarm UNID. Buckets are "000-001", "001-002", "002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".

Memory.C.Current

Histogram of the time (in milliseconds) between a request object being received on the Traveler servlet side and the object being received on the Traveler process side. For example, a stat named IPC_DELAY_PREFIX + "250-500" will hold the number of objects that are between 250 (inclusive) and 500 (exclusive) milliseconds old by the time they are received on the Traveler process side. Buckets are "0000-0250", "0250-0500", "0500-1000", "1000-Inf". Current® C Native memory (MB). Current® Java™ memory (MB).

Memory.Java.Current

The number of users being monitored by the NewAPIMonitor for changes to a user's database.

Monitor.LoopTime.<server name>.<bucket>

The time between successive checks for changes to a users database.

Monitor.NewAPI.Users Monitor.NewAPI.LoopTime

The time (in milliseconds) between successive checks for changes to a user's database, where the database is being monitored by the NewAPIMonitor.

Monitor.Users

The number of users who have the monitoring of their mail database enabled.

NameLookup.Time.Histogram.<returncode>.<bucket>

Histogram of the time (in seconds) to complete the name lookup request. Return code 0 is success and everything else is a failure. Buckets are "000-001", "001-002", "002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".

PrimeSync.Count.<SyncReturnCode>

The number of prime syncs that had the specified return code. The most common return codes are: 200=OK, 408=Request Timeout (Device did not respond before the Server timed out the session), 409=Conflict (Device started a new session which caused this session to be aborted), 500=Unknown Error, 503=Server Busy

PrimeSync.Count.Current

The number of prime syncs that are currently running.

PrimeSync.Count.Large

How many prime syncs have happened where the change count is greater than NTS_PS_CHANGE_THRESHOLD.

PrimeSync.Count.Large.Users

How many users have had large count prime syncs.

PrimeSync.Count.InQueue

The number of prime syncs that are queued up and need to be run but have not started running.

PrimeSync.Time.<SyncReturnCode>.Milliseconds

The amount of milliseconds that the server has spent (total) during prime syncs. Most common return codes are: 200=OK, 408=Request Timeout (Device did not respond before the Server timed out the session), 409=Conflict (Device started a new session which caused this session to be aborted), 500=Unknown Error, 503=Server Busy

PrimeSync.Time.<SyncReturnCode>.Days

The amount of days that the server has spent (total) during prime syncs. This is only present when the Milliseconds becomes too large, so the real value is the combination of the two. The most common return codes are: 200=OK, 408=Request Timeout (Device did not respond before the Server timed out the session), 409=Conflict (Device started a new session which caused this session to be aborted), 500=Unknown Error, 503=Server Busy

PrimeSync.Time.Histogram.<SyncReturnCode>.<bucket>

Histogram of the time spent (in seconds) to complete the prime sync with the given sync return code. The most common return codes are: 200=OK, 408=Request Timeout (Device did not respond before the Server timed out the session), 409=Conflict (Device started a new session which caused this session to be aborted), 500=Unknown Error, 503=Server Busy Buckets are "000-001", "001-002", "002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf"

Push.Users.Total

The total number of users registered with push.

Push.Users.Online

The number of users registered with push that are in the user online state. The user online state means that the user's mail database is actively being monitored for changes; it does not indicate whether or not a device for this user is connected.

Push.Devices.Total

The total number of devices registered with push.

Push.Devices.Online

The number of devices registered with push that are in the device online or status unknown state. These states mean that the user's mail database is actively being monitored for changes for this device; they do not indicate whether or not the device is connected.

Push.Devices.ActiveSync

The number of devices registered for ActiveSync notifications.

Push.Devices.HTTP

The number of devices registered for HTTP notifications.

Push.Devices.SMS

The number of devices registered for SMS notifications.

Push.Devices.TCP

The number of devices registered for TCP notifications.

Push.Devices.ActiveSync.Connected

The number of devices with connected ActiveSync sockets.

Push.Devices.HTTP.Connected

The number of devices with connected HTTP sockets.

Push.Devices.TCP.Connected

The number of devices with connected TCP sockets.

Push.Sent.ActiveSync

The total number of push ActiveSync messages sent.

Push.Received.ActiveSync

The total number of push ActiveSync messages received.

Push.Sent.HTTP

The total number of push HTTP messages sent.

Push.Received.HTTP

The total number of push HTTP messages received.

Push.Sent.SMS

The total number of push SMS messages sent.

Push.Sent.TCP

The total number of push TCP messages sent.

Push.Received.TCP

The total number of push TCP messages received.

Search.Time.Histogram.<bucket>

Histogram stats representing the number of searches that took the defined period of time in LotusTraveler.nsf. Does not apply to HA configurations.

Status.State = <color code>

Color coded (Green, Yellow, Red) indication of the overall status of the IBM Traveler server. tell traveler status gives this code and details on why the state is yellow or red (if one of those color codes is used).

ThreadPool.Count.Max.<thread type>

Maximum number of threads allocated of a particular thread type. tell traveler threads shows this information as well.

ThreadPool.Count.Max.DS

Device Sync

ThreadPool.Count.Max.PS

Prime Sync

ThreadPool.Count.Max.TC

Tell Command

ThreadPool.Count.Max.VC

Validate Cluster

ThreadPool.GetThreadDelayTime.<threadtype>.<bucket>

Histogram of the time spent (in seconds) between a thread being requested and when it actually started running. There are numerous thread types, but some of the more common types are PS (prime sync), DS (device sync), WS(worker system), WD (worker device), TC (tell commands), and Alarm (periodic tasks). Buckets are "00-02", "02-05", "05-10", "10-Inf". For example, the stat ThreadPool.GetThreadDelayTime.PS.01-02 will hold the number of prim esyncs that started with a delay of between 1 (inclusive) and 2 (exclusive) seconds.

TPR.Upload

The total number of TPR (Traveler problem report) uploaded from the devices to the server.

TSS.Assert.Failed

The total number of times an assertion failed in the TSS portion of the server code.

TSS.Assert.Exception

The total number of times an assertion exception occurred in the TSS portion of the server code.

Version

The IBM Traveler Version.

Version.BuildNumber

The IBM Traveler Build Number.