System Analytics

How each of your systems is doing, on one page: tickets, moderation, Auto Moderation, Security, verification, levels, invites, giveaways, reaction roles, temporary voice, social alerts and starboards. Always on.

On this page

Server Analytics is about your members; System Analytics is about the systems that look after them. There is one tab for every system, always. A system that is switched off records nothing, so its tab says so, with a button that switches it on.

How every tab reads

  • Right now is the live state, whatever period is picked: the open ticket queue, the members muted, the giveaways running. It is the first row of tiles, each with a grey icon.
  • In this period is everything the period selector scopes: Today, 7, 30 or 90 days, a year, or all time, the same six as Server Analytics. Each figure carries its change against the period before it.
  • Every figure has a color of its own: the circle on its tile and its chart. A breakdown is one color in shades, the biggest part strongest, with grey for the rest.
  • A line with no data on some days runs on through them in grey instead of breaking.
  • Where a day's total splits into parts (verifications passed and failed, cases filed by staff and by a system), the chart stacks them in one column per day. A breakdown that adds up to one figure (the waiting tickets by age, closes by how they ended, XP by where it came from) is one bar split into its shares.
  • Cyan is a system's main count and green its good or human side: tickets closed, cases filed by staff, alerts posted. Failures are red, refusals and warnings yellow.
  • The members most active in a system are ranked like the public leaderboards, with gold, silver and bronze for the top three.
  • A chart or list with nothing in it yet shows the outline of what will be there, with a note saying what is missing.
  • Days run midnight to midnight in UTC, as on Server Analytics. Today is drawn hour by hour in your own time zone.

What each tab covers

TabWhat it shows
TicketsThe live queue; opened, closed, claimed and reopened; the median time to claim, to the first reply and to close, with their spreads; the reply and close times day by day against the period's average; when tickets arrive; each panel; the lifecycle; queue age; how tickets end and the close reasons; ratings and what members wrote; the most active staff.
ModerationCases by type and by how they were filed (by staff or by a system), the most active moderators, appeals and member reports.
Auto ModerationCatches by filter, and the actions they ran.
SecurityEverything Security acted on, by kind; the anti-nuke limits hit; punishments; changes undone; raids.
VerificationAttempts, passes and failures by method, the pass rate, and why attempts failed: an account too new, too many wrong codes or CAPTCHAs, a role Arclo could not give, or time running out.
LevelsXP earned and where it came from, level-ups, reward roles given, and where members are by level.
Invite TrackingCredited invites against fakes and credited members leaving, how every arrival was counted, and reward roles.
GiveawaysCreated and ended, entries and winners, and the most entered giveaways.
Reaction RolesRoles given and removed, requests a menu's rules turned away and changes Arclo could not make, the most picked roles and the busiest menus.
Temporary VoiceChannels created, the busiest moment, how long channels last, by hub and by member.
Social AlertsAlerts posted and alerts that could not be, across every platform, by platform and by source.
StarboardsMessages starred, stars given, the most starred messages and the members featured most.

Some history starts when Arclo started counting it

Most figures are read from records the systems already keep. Verification outcomes, reaction roles, XP, Auto Moderation catches, Security events, social alerts and temporary voice channels are counted as they happen instead, so for those All time begins on the day Arclo began counting them, not the day you set the system up.

Ticket ratings and written feedback

When a panel asks for ratings, the member's rating request can open a page on arclo.gg with the stars and a box for written feedback. What they write shows up under What members wrote on the Tickets tab, lowest scores first. See Tickets for the two rating styles.

Still stuck? Ask in the support server: somebody there has almost certainly configured this before.