These statistics may be found in multiple components and may be seen multiple times. For example both s2s and c2s will have Bytes received statistic, so each can be found the following way:
s2s/Bytes received c2s/Bytes received
Statistics Name | Description | Statistics Level | Format | Available {field} | List of Possible Statistics |
---|---|---|---|---|---|
add-script last {interval} |
The number of times that |
FINEST |
Integer |
hour |
|
add-script/Average processing time |
The average processing time |
FINEST |
Integer |
|
|
Average processing time on last 100 runs [ms] |
The average processing time in milliseconds for all commands and scripts for this component over the last 100 times component is called. This number will populate with less than 100 runs, and will continue averaging until 100 runs happens, at that point, it’s the most recent 100 instances. This statistic will reset every time the server shuts down or restarts. |
FINEST |
Integer |
|
|
Bytes received |
The total number of bytes that the component has received during the current server instance. This statistic resets at server shutdown or restart. |
FINE or FINEST |
Integer |
|
|
Bytes sent |
The total number of bytes that the component has sent during the current server instance. This statistic resets at server shutdown or restart. |
FINE or FINEST |
Integer |
|
|
del-script last {interval} |
The number of times that |
FINEST |
Integer |
hour |
|
del-script Average processing time |
The average time in ms, returned as an integer, it takes for |
FINEST |
Integer |
|
|
Last {interval} packets |
The number of packets that have been handled by this component in the last interval. |
FINEST |
Integer |
hour |
|
List-commands last {interval} |
The number of |
FINEST |
Integer |
hour |
|
List-commands Average processing time |
The average time in ms, returned as an integer, it takes for |
FINEST |
Integer |
|
|
{IN/OUT/Total} queue overflow |
The number of times the in or out queue has overflown for this component. That is there are more packets queues than the max queue size. A total statistic is also available that combines both results. |
FINEST |
Integer |
|
|
{in/out} queue wait: {priority} |
The number of packets with {priority} priority currently in the incoming or outgoing queue. |
FINEST |
Integer |
SYSTEM |
|
{IN/OUT}_QUEUE processed {type} |
The number of stanzas of different types that have been processed VIA the In or Out Queue of this component. This number will reset at the end of the server instance. Each component will have a list of the different types of stanzas it can process. |
FINER |
Integer |
# |
|
NOTE: Several statistics are only available from statistics component, shutdown thread will ONLY print the following: messages, presences, cluster, other, IQ no XLMNS, total IQ. |
|||||
max queue size |
The maximum number of items allowed in the packet queue for this component. |
FINEST |
Integer |
|
|
Open Connections |
The number of open connections to the component. |
INFO/FINEST |
Integer |
|
|
Packets received |
The total number of packets received by the component from external sources in the current instance. This number resets at server shutdown or restart. |
FINE |
Integer |
|
|
Packets sent |
The total number of packets sent by the component in the current instance. This number resets at server shutdown or restart. |
FINE |
Integer |
|
|
Processed packets thread: {in/out} |
How many packets have been processed in and out by each processing thread. |
FINEST |
Integer |
|
|
Statistics will provide an array for each processor, listed from 0, 1, 2, 3 etc..
Let’s say that we have 4 threads set for ws2s, a list will be seen like this:
|
|||||
processing threads |
The number of threads provided for the particular component. |
FINER |
Integer |
|
|
stream-error-counter |
The number of errors counted during the operation of the server for this component. Will only be available if stream-error-counter is enabled in config.tdsl, otherwise will be 0. |
FINE |
Integer |
|
|
Socket overflow |
The number of times that this component has experienced socket overflow and had to drop packets. This does not include the number of dropped packets. |
FINEST |
Integer |
|
|
Total {in/out} queues wait |
The number of packets in the inbound or outbound queue that are currently waiting to be sent. This includes packets of all types. This is an instant statistics, in that the number in queue is only as many in the queue the moment statistics are gathered. |
FINEST |
Integer |
|
|
Total queue wait |
A combined total of |
FINEST |
Integer |
|
|
Total queues wait |
A combined total of all component queue wait statistics. |
FINEST |
Integer |
|
|
Total queues overflow |
The number of times the component packet wait queue has overflown and had to drop packets. This statistic does not keep track of the number of dropped packets. |
FINEST |
Integer |
|
|
Total/Total queues overflow |
The combined total of all queue overflow statistics for all components. |
FINEST |
Integer |
|
|
Waiting to send |
The number of packets in the component’s queue that are waiting to be sent. This number will usually be 0 however it will grow if a large number of packets are jamming up your system, or your queue sizes are set too low. |
FINEST |
Integer |
|
|
Watchdog runs |
The number of times watchdog has been run on this component to check for stale connections. |
FINER |
Integer |
|
|
Watchdog stopped |
The number of times watchdog identified and closed a connection it has found to be stale according to the settings in |
FINER |
Integer |
|
|
Watchdog tests |
The number of times watchdog has found a potential stale connection and has conducted a test to determine whether or not to close the connection. This is per component in the current server instance. |
FINER |
Integer |
|
|