Tigase Administration Guide
Statistics description

The number of times that add-script adhoc command has been run within the last interval.

Available {interval}: hour|minute|second

Statistics Level: FINEST

Result Format: Integer

Sub-level Statistics Available:

add-script/Average processing time: The average time in ms, returned as an integer, it takes for add-script to execute.

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/adhoc-command/add-script last hour
{compname}/adhoc-command/add-script last minute
{compname}/adhoc-command/add-script last second
{compname}/adhoc-command/add-script/Average processing time

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.

Statistics Level: FINEST

Result Format: Integer

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/Average processing time on last 100 runs [ms]

The total number of bytes that the component has received during the current server instance. This statistic resets at server shutdown or restart.

Statistics Level: FINE|FINEST

c2s is FINE, all others are FINEST

Result Format: Integer

Available from the following components:

bosh, c2s, cl-comp, proxy, s2s, ws2s

List of possible statistics:

{compname}/Bytes received

The total number of bytes that the component has sent during the current server instance. This statistic resets at server shutdown or restart.

Statistics Level: FINE|FINEST

c2s is FINE, all others are FINEST

Result Format: Integer

Available from the following components:

bosh, c2s, cl-comp, proxy, s2s, ws2s

List of possible statistics:

{compname}/Bytes sent

The number of times that del-script adhoc command has been run within the last interval.

Available {interval}: hour|minute|second

Statistics Level: FINEST

Result Format: Integer

Sub-level Statistics Available:

del-script/Average processing time: The average time in ms, returned as an integer, it takes for del-script to execute.

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/adhoc-command/del-script last hour
{compname}/adhoc-command/del-script last minute
{compname}/adhoc-command/del-script last second
{compname}/adhoc-command/del-script/Average processing time

The number of packets that have been handled by this component in the last interval.

Available {interval}: hour|minute|second

Statistics Level: FINEST

Result Format: Integer

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/last hour packets
{compname}/last minute packets
{compname}/last second packets

The number of list-commands requests sent to the component in the last interval.

Available {interval}: hour|minute|second

Statistics Level: FINEST

Result Format: Integer

Sub-level Statistics Available:

list-commands/Average processing time: The average time in ms, returned as an integer, it takes for list-commands to execute.

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/list-commands last hour
{compname}/list-commands last minute
{compname}/list-commands last second
{compname}/list-commands/Average processing time

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.

Statistics Level: FINEST

Result Format: Integer

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/IN queue overflow
{compname}/OUT queue overflow
{compname}/Total queue overflow

The number of packets with {priority} priority currently in the incoming or outgoing queue.

Available {priority}: SYSTEM|CLUSTER|HIGH|NORMAL|LOW|PRESENCE|LOWEST

Statistics Level: FINEST

Result Format: Integer

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/In queue wait: SYSTEM
{compname}/In queue wait: CLUSTER
{compname}/In queue wait: HIGH
{compname}/In queue wait: NORMAL
{compname}/In queue wait: LOW
{compname}/In queue wait: PRESENCE
{compname}/In queue wait: LOWEST
{compname}/Out queue wait: SYSTEM
{compname}/Out queue wait: CLUSTER
{compname}/Out queue wait: HIGH
{compname}/Out queue wait: NORMAL
{compname}/Out queue wait: LOW
{compname}/Out queue wait: PRESENCE
{compname}/Out queue wait: LOWEST

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.

Available {type}:

messages
presences
cluster
other
IQ no XMLNS
IQ http://jabber.org/protocol/disco#items
IQ bind
IQ jabber:iq:roster
IQ session
IQ vCard
IQ command
IQ jabber:iq:private
IQ http://jabber.org/protocol/disco#info
total IQ

Statistics Level: FINER

Result Format: Integer

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/IN_QUEUE processed messages
{compname}/IN_QUEUE processed presences
{compname}/IN_QUEUE processed cluster
{compname}/IN_QUEUE processed other
{compname}/IN_QUEUE processed IQ no XMLNS
{compname}/IN_QUEUE processed IQ http://jabber.org/protocol/disco#items
{compname}/IN_QUEUE processed IQ http://jabber.org/protocol/disco#info
{compname}/IN_QUEUE processed IQ bind
{compname}/IN_QUEUE processed IQ jabber:iq:roster
{compname}/IN_QUEUE processed IQ jabber:iq:private
{compname}/IN_QUEUE processed IQ session
{compname}/IN_QUEUE processed IQ vCard
{compname}/IN_QUEUE processed IQ command
{compname}/IN_QUEUE processed total IQ
{compname}/OUT_QUEUE processed messages
{compname}/OUT_QUEUE processed presences
{compname}/OUT_QUEUE processed cluster
{compname}/OUT_QUEUE processed other
{compname}/OUT_QUEUE processed IQ no XMLNS
{compname}/OUT_QUEUE processed IQ http://jabber.org/protocol/disco#items
{compname}/OUT_QUEUE processed IQ http://jabber.org/protocol/disco#info
{compname}/OUT_QUEUE processed IQ bind
{compname}/OUT_QUEUE processed IQ jabber:iq:roster
{compname}/OUT_QUEUE processed IQ jabber:iq:private
{compname}/OUT_QUEUE processed IQ session
{compname}/OUT_QUEUE processed IQ vCard
{compname}/OUT_QUEUE processed IQ command
{compname}/OUT_QUEUE processed total IQ

The maximum number of items allowed in the packet queue for this component.

Statistics Level:

Result Format: Integer

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, muc, monitor, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/max queue size

The number of open connections to the component.

Statistics Level: INFO|FINEST

c2s is INFO, all other components are FINEST

Result Format: Integer

Available from the following components:

bosh, c2s, cl-comp, proxy, s2s, ws2s

List of possible statistics:

{compname}/Open connections

The total number of packets received by the component from external sources in the current instance. This number resets at server shutdown or restart.

Statistics Level: FINE

Result Format: Integer

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/Packets received

The total number of packets sent by the component in the current instance. This number resets at server shutdown or restart.

Statistics Level: FINE

Result Format: Integer

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/Packets sent

How many packets have been processed in and out by each processing thread. 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:

ws2s/Processed packets thread: IN=[2, 6, 4, 2]
ws2s/Processed packets thread: OUT=[8, 0, 1, 3]
ws2s/Processed packets thread (outliers) IN=mean: 79.0, deviation: 441, outliers: [in_10-ws2s: 2359]
ws2s/Processed packets thread (outliers) OUT=mean: 16.5, deviation: 23.2058941, outliers: [out_ws2s: 80]

Note that the processor arrray will only have as many threads as the component has as defined in {compname}/Processing threads.

Statistics Level: FINEST

Result Format: Integer

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, pubsub, proxy, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/Processed packets thread: IN
{compname}/Processed packets thread: OUT
{compname}/Processed packets thread (outliers) IN
{compname}/Processed packets thread (outliers) OUT

The number of threads provided for the particular component.

Statistics Level: FINER

Result Format: Integer

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/processing threads

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.

Statistics Level: FINEST

Result Format: Integer

Available from the following components:

bosh, c2s, cl-comp, proxy, s2s, ws2s

List of possible statistics:

{compname}/Socket overflow

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.

Related Statistics: {compname}/Total queue wait: A combined total of Total in queue wait and Total out queue wait statistics for this component. Total queues wait: A combined total of all component queue wait statistics.

Statistics Level: FINEST

Result Format: Integer

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, muc, monitor, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/Total in queues wait
{compname}/Total out queues wait
{compname}/Total queues wait
Total queues wait

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.

Related Statistics: total/Total queues overflow: The combined total of all queue overflow statistics for all components.

Statistics Level: FINEST

Result Format: Integer

Available from the following components:

amp, bosh, c2s, cl-comp, eventbus, message-archive, message-router, monitor, muc, proxy, pubsub, rest, s2s, sess-man, ws2s

List of possible statistics:

{compname}/Total queues overflow
total/Total queues overflow

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.

Statistics Level: FINEST

Result Format: Integer

Available from the following components:

bosh, c2s, cl-comp, proxy, s2s, ws2s

List of possible statistics:

{compname}/Waiting to send

The number of times watchdog has been run on this component to check for stale connections.

Statistics Level: FINER

Result Format: Integer

Available from the following components:

bosh, c2s, cl-comp, s2s, ws2s

List of possible statistics:

{compname}/Watchdog runs

The number of times watchdog identified and closed a connection it has found to be stale according to the settings in init.properties or by the defaults defined in this section.

Statistics Level: FINER

Result Format: Integer

Available from the following components:

bosh, cl-comp, c2s, s2s, ws2s

List of possible statistics:

{compname}/Watchdog stopped

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.

Statistics Level: FINER

Result Format: Integer

Available from the following components:

bosh, cl-comp, c2s, s2s, ws2s

List of possible statistics:

{compname}/Watchdog tests