Logging

Logging is the system every other system reports into, and the first thing worth setting up. It has no master switch: a server with no log channel is already logging nothing, so a switch would be a second way of saying the same thing.

1Setting it up

1. 1

   Open General → Logging

   The page has 4 tabs: Event Logs, System Logs, General Settings, Commands.

2. 2

   Set a default channel

   On General Settings, choose where anything without a channel of its own should go. One private staff channel is a fine start.

3. 3

   Or let Arclo build the channels for you

   Set up my log channels creates a private arclo logs category with one channel per log category, skipping any category that already has one.

4. 4

   Turn on the categories you want

   Each category has a switch, and so does each event inside it. Both must be on for a line to be delivered.

2Event Logs

The gateway events — everything that happens in Discord, whether or not Arclo did it.

• Each card carries a colored hairline saying what kind of line it is: green made something, red removed something, yellow changed something.
• Cards marked Needs audit log can only name who did it if Arclo has View Audit Log. Without it the line still posts, saying what happened but not who.
• Cards marked Noisy fire often. They are off by default for a reason.

Routing

Arclo resolves a destination most-specific-first, and the same resolver answers the “where does this go?” chip on the dashboard, so the page can never promise a channel the bot would not use.

the event's own channel  →  its category's channel  →  the default channel

3System Logs

The other half: what Arclo did. Every system has one logger with its own switch, its own channel and a switch per action — “Ticket claimed”, “Reward failed”, “Sticky reposted”.

• The structure mirrors Event Logs exactly: system is to action what category is to event, and the routing rule is the same one.
• There is one logger per system, not one per configuration. Four verification panels share one verification logger.
• The same controls appear on each system's own page, at the bottom. Editing from either place edits the same record.
• A switched-off logger hides its channel and its action list rather than dimming them — there is nothing there to configure while it is off.

4General settings

Default channel

The fallback destination for anything without a channel of its own.

Ignored channels

Nothing happening in these channels is logged. Ignoring a category ignores its channels.

Ignored roles

Actions by members holding one of these are not logged.

Ignored members

Specific people — usually other bots you have already made noisy.

Ignore bots / ignore Arclo

Two switches, because “do not log other bots” and “do not log yourself” are different wishes.

Ignored prefixes

Messages starting with these are skipped — the standard way to keep another bot's commands out of your message log.

Delivery

Lines are sent through a webhook by default, which is faster and has its own rate limit. Name and avatar are yours to set.

Appearance

The look of the log embeds themselves.

Behaviour

• Lines are batched. They buffer for just over a second and send up to ten at a time, so a raid or a purge does not put your log channel minutes behind.
• A kick and a ban both arrive as a member leaving. Arclo waits a moment for the audit-log entry that explains which it was, so a ban logs once and a kick logs at all.
• Timestamps render in the reader's own time zone — they are Discord timestamps, not baked text, so there is no log time zone to set.
• A broken webhook is retried. A channel Arclo cannot post to is marked and retried a few minutes later, because the fix happens in Discord where the bot never hears about it.
• Arclo reports its own permission problems. “Why did the welcome message stop sending?” gets an answer in your log channel, at most once an hour per permission.

Commands