The following table lists and explains the various statistics that can result from
|
|
|
|
|
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%.
|
|
|
How many times a ntsclcache database was accessed.
|
|
|
How many times a ntsclcache database entry was deleted.
|
|
|
Whether or not Traveler is currently in the constrained state.
|
|
|
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".
|
|
|
The total number of connections currently allocated.
|
|
|
The number of currently allocated connections available for new work.
|
|
|
The maximum number of connections that could be allocated.
|
|
|
The number of times the access rights were checked for a database using the Domino® C API call.
|
|
|
The number of times a database was closed using the Domino C API call.
|
|
|
The number of times a database was opened using the Domino C API call.
|
|
|
The number of times a note was closed using the Domino C API call.
|
|
|
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 DCA.C.HTMLDestroyConverter
|
The number of times an HTML Converter object was created.
|
|
|
Count of the number of times Lotus Notes® Traveler had to determine which documents were changed.
|
|
|
The number of documents that Lotus Notes 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.
|
|
|
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).
|
|
|
The number of times directory lookup is performed.
|
|
|
The number of times directory lookup is performed.
|
|
|
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".
|
|
|
The number of times a database was closed using the Domino Java™ API.
|
|
|
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".
|
|
|
The number of times a document was closed using the Domino Java API.
|
|
|
The number of times a document was opened using the Domino Java API.
|
Database.Query.Histogram.<query>.<bucket>
|
Histogram of the time spent (in seconds) to execute the specified query against Traveler's internal database. Query is the query that was executed. Buckets are "000-001", "001-002", "002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".
|
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".
|
|
|
The total number of bytes received from devices during sync operations.
|
|
|
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.
|
|
|
The total number of bytes sent to devices during sync operations.
|
|
|
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.
|
|
|
Name of the last user to finish a Device Sync.
|
|
|
Date of the last Device Sync.
|
|
|
Time of the last Device Sync.
|
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".
|
|
|
Number of errors logged (total).
|
|
|
Number of errors logged for the specified user.
|
GetAlarm.Time.Histogram.<bucket>
|
Number of errors logged for the specified type.
|
|
|
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".
|
|
|
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).
|
|
|
The number of users being monitored by the NewAPIMonitor for changes to a user's 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.
|
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".
|
|
|
The number of prime syncs that are queued up and need to be run but have not started running.
|
|
|
The number of prime syncs that are currently running.
|
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.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"
|
|
|
The total number of users registered with push.
|
|
|
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.
|
|
|
The total number of devices registered with push.
|
|
|
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.
|
|
|
The number of devices registered for ActiveSync notifications.
|
|
|
The number of devices registered for HTTP notifications.
|
|
|
The number of devices registered for SMS notifications.
|
|
|
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.
|
|
|
The total number of push ActiveSync messages sent.
|
|
|
The total number of push ActiveSync messages received.
|
|
|
The total number of push HTTP messages sent.
|
|
|
The total number of push HTTP messages received.
|
|
|
The total number of push SMS messages sent.
|
|
|
The total number of push TCP messages sent.
|
|
|
The total number of push TCP messages received.
|
ThreadPool.GetThreadDelayTime.<threadtype>.<bucket>
|
Histogram of the time spent (in seconds) between a thread being requested and when it actually started running. Thread types are PS (prime sync), DS (device sync), Worker (general usage), 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.
|
|
|
The total number of TPR (Traveler problem report) uploaded from the devices to the server.
|
|
|
The total number of times an assertion failed in the TSS portion of the server code.
|
|
|
The total number of times an assertion exception occurred in the TSS portion of the server code.
|
|
|
The Lotus Notes Traveler Version.
|
|
|
The Lotus Notes Traveler Build Number.
|