Statistics

Live

What the server went through, day by day.

What is counted

Counters run continuously and are written to the database every five minutes. Each event costs one write in memory, not a transaction — counting slows nothing down.

Measure	What it tells
`messages`	Number of messages written during the day
`activeMembers`	Distinct people who wrote at least once
`joins / leaves`	Joins and leaves
`sanctions`	Cases opened, commands and AutoMod together
`commandsUsed`	Commands run
`members`	Member count at the last update

The module is on from installation. Statistics are only worth their history, and it does not start retroactively: turning it on three months later would not bring back the three months gone by.

How active members are counted

A person counts once per day, however many messages they write. It is the measure that says whether a server is alive: a thousand messages from three people and a thousand from two hundred do not describe the same community.

The count is approximate to within 1%. Keeping the exact list of active members would cost several megabytes a day on a large server, for a figure nobody reads to the unit.

Per-channel detail

Off by default: the server total is enough for most teams, and counting per channel doubles the write cost of every message. When on, it produces the ranking of the most active channels.

This detail lives in memory, never in the database: one line per channel per day would multiply the volume by the number of channels, for information looked at once a month. The ranking therefore never goes back more than seven days, even when choosing a longer period.

Reading the figures

The dashboard’s Statistics page covers 7, 30 or 90 days. Days without activity have no line in the database: they are filled in on display, otherwise a curve would jump from one date to the next while giving the illusion of continuity.

Net growth is the only honest way to sum up a month: a server that gains a thousand members and loses a thousand has not grown.