cordavix statistics --overview
Server activity that counts itself
The bot counts messages, joins, leaves and voice time on the fly in Redis - in the dashboard you choose the period and see the trend as metrics and a chart.
Depiction: metric tiles for messages, joins and voice time with placeholder values, and below them a recreation of the curve from the dashboard's "Messages per day" chart - without real numbers or axis labels.
How the statistics work
Four events count automatically
Messages (bots excluded), joins, leaves and voice time increment a counter on every matching Discord event - voice minutes per session are capped at twelve hours, and all of it only runs while the "Statistics" module is enabled for the server.
The bot counts only in Redis
Every event increments a daily counter there under the key stats:<guildId>:<date>; per the code comment, a Redis outage must never disrupt the event flow - a daily worker job atomically moves the counters (via RENAME) into the database, so no increments are lost even with parallel runs.
Retention depends on the plan
How long statistics are kept depends on the plan; a daily job automatically deletes older entries, and the dashboard's period picker is capped server-side to exactly that retention.
Only daily totals, no individual data
Only one row per server and calendar day is stored, holding the four counters and the end-of-day member count - no user IDs and no message content.
Evaluated as metrics and charts in the dashboard
Tiles for messages, joins, leaves, voice time and member count sit alongside a line chart for messages per day and a bar chart for joins and leaves - selectable over 7, 30 or 90-day periods.
Statistics retention: 7 days in the free plan, 30 days from Basic, 180 days from Pro.
Know how your server is doing
Turn on statistics for free and see your server in numbers.