STATS

Usage: STATS <option> [<server>]

Shows statistics for the server you designate, if you don't specifically designate a server it defaults to the server you are on.

The option parameter can be one of the following:

c - Connections, D - Domain reporting, h - Hubs, i - Allowed hosts, j - Client type count, k - Automatic kills, K - Additional security information,
l - Links, m - Command usage, o - Operator list, P - Proxy status, q - Qlines, Q - Send queue, u - Server Uptime, U - Unknown connections, w - User statistics,
Z - Internal information, 1 - Memory stats, 2 - System stats, 4 - Resolver information, 5 - Version history

Examples:

/stats k

/stats k chat.confrooms.org

/hs stats 5

/hs stats x

Usage: STATS 1 [<server>]

Memory statistics - On windows systems ConferenceRooms can give certain memory statistics for the Operating System, including: Memory Load, Free Physical Memory, Page file in use, Configured Working Set Size, Working Set Size, Process Pagefile Use, Process Paged Pool Use and Process NonPaged Pool Use Statistics.

Examples:

/stats 1

/stats 1 chat.*

Note: this will only work if CR is running on a windows system.

Usage: STATS 2 [<server>]

Memory statistics - On windows systems ConferenceRooms can give certain memory statistics for the Operating System including: Memory Load, Free Physical Memory, Page file in use, Compressing Heap, Memory Load, Free Physical Memory and Page file in use.

Examples:

/stats 2

/stats 2 chat.*

Usage: STATS 4

Resolver Information: - Shows the active resolvers that have been specifically defined. It also shows the penalty count for wach name server. The higher the penalty count the less we use that specific name server.

Examples:

/stats 4

/stats 4 chat.*

Usage: STATS 5 [<server>]

Version history: - This is primarily useful if you need technical support on beta code as it shows us the internal version of each module inside of ConferenceRooms.

Examples:

/stats 5

/stats 5 chat.*

STATS c

Usage: STATS c

Connections: - Shows all the servers that are configured and enabled. Contains their server name, address and connection port.

Examples:

/stats c

/stats c chat.*

Usage: STATS D

Domain reporting: - Gives you a list of the configured servers and the last time a domain report was sent.

Examples:

/stats D

STATS h

Usage: STATS h [<server>]

Hubs: - This will show you which hubs you are configured to connect to.

Examples:

/stats h

/stats h chat.*

STATS i

Usage: STATS i [<server>]

Allowed Hosts: - Shows all of the user@host masks that are allowed to connect to the server. It will also show the ping time that the mask contains.

Examples:

/stats i

/stats i chat.*

STATS j

Usage: STATS j [<server>]

Client type count: - This will give you a client type breakdown for both local and global clients.

Examples:

/stats j

/stats j chat.*

Usage: STATS K [<server>]

Additional security information: - This will list some Zline, Proxy and URL filtering settings, as well as some connection statistics of the server.

Examples:

/stats K

/stats K chat.*

STATS l

Usage: STATS l [<server>]

Links: - Shows all the active server links of the target server.

Examples:

/stats l

/stats l chat.*

STATS m

Usage: STATS m [<server>]

Commands: - It will give a list of commands and how many times each has been used. This may be useful to make sure that certain commands aren't being overused or misused. For example, if your network requires opers to send an email explaining every shun and the total shun count has gone up more than the emails received, then you can look for the discrepancy.

Examples:

/stats m

/stats m chat.*

STATS o

Usage: STATS o [<server>]

Operators: - Shows the operator configurations for the target server. You will get a list of masks and nicks that are allowed to oper. To the left of each entry will be a letter that shows their status, such as h for helper or O for oper.

Examples:

/stats o

/stats o chat.*

Usage: STATS P [<server>]

Proxy status: - Gives you a list of the hosts that have been caught by the proxy filter along with the number of attempts that each host has made.

Examples:

/stats P

/stats P chat.*

STATS q

Usage: STATS q [<server>]

Usage: STATS Q [<server>]

Qlines: - Shows all of the nicknames that cannot be used by non-opers and why they are prohibited. See QLINE to add such nicks.

Send queue: - Shows queue information. This will usually not be very useful but can contain information needed for debugging.

Examples:

/stats q

/stats q chat.*

STATS u

Usage: STATS u [<server>]

Usage: STATS U [<server>]

Uptime: u - Shows how long the server has been running.

Unknown connections: U - See the IP addresses of the unknown connections to your server. Connections can be open for a variety of reasons. Most common is that the client is waiting for DNS resolving to happen. You can close these connections with the CLOSE command.

Examples:

/stats u

/stats u chat.*

/stats U

/stats U chat.*

Usage: STATS V [<server>]

Video Statistics:

This will give you the current status of the streaming server including version, if it's active and communicating properly with the chat server as well as statistical information on the number of streams and users per stream that are currently in use.

Example:

/stats V conferencerooms.*

/stats V

STATS w

Usage: STATS w [<server>]

User statistics: - Shows the average number of network operators and users on that server and on the network for various recent time intervals. This is a good way to keep track of how your network is doing and look for problems. You can check your oper to user ratio and make sure that it is sufficient for the times your chat network is open.

Examples:

/stats w

/stats w chat.*

STATS x

Usage: STATS x [<server>]

Server statistics: - Shows all the servers that you have defined and enabled but that are not currently connected to the target server.

Examples:

/stats x

/stats x chat.*

Usage: STATS Z [<server>]

Internal Information:

This is not very useful to the user, but it is important debugging information. If you email support@conferencerooms.org for technical support you should give the stats Z and Stats 5 of the server or of services.* if the problem is a services problem.

Example:

/stats Z conferencerooms.*

/stats Z