Web Analytics and Audit Log

NeatQueue records server activity to an event log, and the web dashboard's Analytics page shows it with charts, filters, and search. This is where you go to answer questions like "who changed the result of that match?" or "who banned this player?".

Opening the Analytics page

Go to neatqueue.com, sign in with Discord, and open your server's Analytics page (/analytics/<server id>). You need a configured NeatQueue Staff Role or Manage Channels permission on the server.

The top of the page summarizes the selected date range:

• Total Matches, Unique Players, Queues Played, Avg / Day
• Peak Hour and Peak Day
• Charts for matches and active players over time, activity by hour and weekday, matches by queue, and a queue funnel (joins → filled → started → completed)

The Event Log

Below the charts is the Event Log — the server's audit log. Each row shows:

Column	What it is
Time	When the event happened
Event	The event type, e.g. COMMAND EXECUTE, MATCH CANCELLED, QUEUE JOIN, BAN ADD
User	Who performed the action
Details	The command name, queue, match number, winner, or amount

Every slash command is recorded with the member who ran it, so admin actions like /outcome selectwinner, /outcome tie, /outcome cancel, /managestats reset, and /player ban are all attributable after the fact.

Filtering

• Event Type — narrow to one type of event
• User — a Discord user ID or name
• Search — free text across the command, user, and description
• Date range — set at the top of the Analytics page; it applies to the log too

Results are paginated 50 at a time, and the filters live in the URL, so a filtered view can be bookmarked or shared with other staff.

Finding who changed a match result

1. Open the Analytics page for your server.
2. Set the date range to cover when the change happened.
3. In the Event Log, search for outcome (or filter Event Type to COMMAND EXECUTE).
4. The User column on the matching row is who ran the command.

If you know the member already, put their ID or name in the User box instead to see everything they did.

In Discord

For a quick look without leaving Discord, use /logs:

/logs (filter)

It prints the same events in chronological order, with an optional word filter matching the command, user, event type, or description. The web Event Log is the better tool when you need date ranges, pagination, or search — but /logs is faster for a quick check.

note

The event log only covers activity recorded since event tracking was added. Older matches still appear in match history, but there may be no event rows attributing changes made before then.