Skip to content
Athena User Guide
Esc
↑↓navigate↵open⌘Jpreview
On this page

Monitor a live event

Watch participants, submissions, running instances, and usage while your event is live.

Once your event is live, the event dashboard gives you six vantage points: the Overview, the Players list, the Leaderboard, the Running instances table, the Submissions log, and the per-event Usage page.

These pages load a snapshot of the moment you open them; nothing auto-refreshes, so reload the page for fresh numbers.

Overview

The event’s landing page in the dashboard opens with an Event details card (status, event URL with an Open event button, the address your event’s mail is sent from, plan, storage size, team mode, duration, flag prefix, and the start, scoreboard freeze, and end times), followed by four stat cards:

  • Total Users: registered users
  • Challenges: every challenge on the event, drafts and hidden ones included, so it is an authoring total rather than what players can see
  • Submissions: total flag attempts
  • Success rate: the share of submissions that were correct

Below them, a Challenges by category chart breaks down your published set, and Submissions over time plots the daily submission count across your whole event window. For deeper analysis (attempt distributions, per-challenge solve rates, exports), use the Analytics page, covered in Export event data.

Players

The Players page lists every registered participant with their name, handle (@username), email, and points, plus their team when the event runs in team mode. Search by name, handle, email, or team name, sort by name or points, and page through the roster 25 rows at a time, up to 100 with the page-size selector. The search term, sort, page and page size all live in the URL, so a filtered view is shareable.

Two things to know when reading it:

  • Points is the participant’s team score: in team mode, every member of a team shows the same number.
  • Rows open a detail sheet. Click a participant to see their activity stats, points progression, and solve/submission/hint/instance history, and to adjust their points (a signed bonus or penalty with a required reason, applied to their whole team; it can’t drop the team below zero). The sheet also carries the participant-management actions: Ban player, Remove from team, and Delete player.

Leaderboard

The Leaderboard page shows the event’s current standings: a Rank / Name / Points / Solves table, topped by a Top 10 score progression chart once there’s enough history to plot. Like the rest of the dashboard, it’s a snapshot at load; reload for the latest.

This is your organizer view of the standings, and it differs from the public scoreboard players see in two ways:

  • It’s never labeled frozen. After the scoreboard freeze, the players’ public board stops updating and is marked as final; your Leaderboard keeps showing the live standings. (In practice the numbers match, since flag submissions also close at the freeze, so scores don’t move afterward either.)
  • It includes hidden teams. Teams hidden from the public scoreboard still appear here, so you always see the complete ranking.

If the standings look wrong

Occasionally the standings here can disagree with the scores recorded for each team: a team’s points don’t match the total on their detail sheet, or a solve doesn’t move anyone’s rank.

Rebuild leaderboard, in the page header, re-derives every team’s rank and solve count from the event’s recorded results and refreshes each team’s points from their recorded total. It asks for confirmation, tells you how many teams it covered, and appears in the event’s Audit log.

Nothing is at risk: each team’s points, solves and score history are read, never rewritten; a rebuild only refreshes what the standings display. Running it when nothing is wrong leaves the board exactly as it was, so you can run it as often as you like. Players see the corrected board on their next reload.

Running instances

The Running instances page tracks every challenge instance your players have started: one row per instance with the challenge, the user who started it, its status (such as running, failed, terminated, or expired), and when it was created.

Clicking a row opens the Challenge session details dialog with the full picture: the session ID, the challenge and user, one endpoint per exposed port with the hostname players connect to, its timestamps (created, updated, expires, and terminated), and its metering and resources. That last block shows when metering started and ended, the task size as CPU units and memory, the billing multiplier, and a Shut down row showing when the instance released its resources or Still finishing if it hasn’t. For instances that failed, the dialog shows a generic issue notice rather than technical error output.

Players start and stop their own instances, and instances expire on their own, so day to day there’s nothing to do here. When you do need to intervene, the details dialog offers Terminate instance for a single session, and the page header offers Terminate all (N) for every running instance across the event. Both buttons appear only while there is something running to stop. Terminating frees the instance’s resources and returns its credit reservation; the team can deploy again afterwards. Both actions ask for confirmation and appear in the event’s Audit log.

The page also shows a banner naming any instances that may still be running after being marked terminated, listing the affected session IDs. Cleanup retries automatically and usually clears within a few minutes; if entries persist, contact support with those IDs.

Submissions

The Submissions page is a log of flag attempts: each row shows the user, the challenge, the result (Correct or Incorrect), and when it was submitted, with search and a correct/incorrect filter. Submitted flag text is never displayed.

The page is paginated at 15 rows per page by default (up to 100 with the page-size selector), and pages through every submission, not just recent ones. For aggregate, event-wide submission statistics, export a report from the Analytics page.

Usage

The per-event Usage page scopes resource consumption to this one event, over its whole life:

  • Consumed IH: instance-hours consumed by this event
  • Open sessions: instances running right now, with the credits reserved against them
  • Credits remaining: the workspace wallet balance
  • Usage events: metering events recorded for the event
  • Active users: distinct users with metered activity
  • Last metered event: the most recent usage timestamp
  • Storage used: space consumed, with a Storage utilization bar showing it against the event’s storage limit

Usage figures update periodically as metering data arrives, not in real time. Workspace-wide usage and overage across all your events live on the workspace Usage page; see Manage billing and credits.

Was this page helpful?