Logging
Every moderation and server-activity event can be routed to its own channel: 30+ distinct Discord events across seven categories, with each category switched to a shared Default channel or off.
How It Works
Aegis logs 33 event types across seven groups: moderation, automod, members, messages, voice, server changes and tickets.
Events are grouped into categories (Moderation, Safety, Admin, Messages, Misc, Members and Server), and each category has one switch: send it to the Default Log Channel, or don't log it. Most servers set a Default, leave the categories they want on, and switch off the ones they don't care about.
Any single event can still be pointed at a channel of its own, and that always wins. It goes where you point it whatever its category's switch says. That is how you break a high-traffic type like Voice Activity or Messages out into its own channel while everything else keeps flowing to the Default.
So an event goes to: its own channel if it has one, otherwise the Default channel if its category is switched on, otherwise nowhere.
All logs share a small built-in delay (a few seconds) so Discord's audit log has time to resolve who actually performed an action before Aegis posts about it.
Event Categories
Grouped on the dashboard for readability; each row is still an independent channel picker.
| Group | Events |
|---|---|
| Messages | Message Deleted, Message Edited |
| Members | Nickname Change, Username Changed, Display Name Changed, Avatar Changed, Member Role Changed, Member Joined, Member Left (covers leave/kick/ban with the same event) |
| Server | Server Settings, Roles, Channels, Emoji & Stickers, Server Boost, Invites |
| Safety | AutoMod, Anti-Scam, Raid Defense, Honeypot, Verification |
| Moderation | Kick, Mute, Timeout, Warn, Unwarn |
| Admin | Ban, Unban, Purge |
| Misc | Voice Activity, Ticket Closed, Dynamic VC (Temp Voice), Game Servers Logs, Server Setup |
A channel-level blacklist lets you exclude specific channels from Message Deleted/Edited logging entirely, which is useful for bot-spam or logging channels that would otherwise flood themselves.
What Gets Logged
Coverage runs deeper than the category names suggest, for example "Channels" covers create/delete/update and permission-overwrite changes (with a full before→after per permission), "Roles" covers create/delete/update including permission diffs, and "Server Settings" covers name/icon/verification level/AFK settings and Discord's newer onboarding/Server Guide changes too.
Message Deleted and Message Edited logs quote the original content as a blockquote rather than a code block, so any @mentions inside it render normally instead of showing a raw user ID. Every other value in a log embed is inline code rather than a fenced block, which keeps an embed readable at a glance instead of a column of boxes.
When AutoMod removes a message, the Message Deleted log is footed AutoMod with the filter that caught it, and carries the reason, not the person who wrote the message. Discord's audit entry for a bot deletion arrives too late to rely on, so AutoMod says so itself before deleting.
Game Servers Logs covers the full lifecycle of a Game Server Group: role/category/channel creation as one combined entry, locking/unlocking, members joining/leaving, and closing. It is kept separate from the generic Channels/Roles/Members categories so it doesn't get lost among unrelated server activity.
Server Setup covers messages posted through the /server-setup menu, recording who sent one, which channel it went to, whether it was plain or an embed, and a jump link to the message itself. Configuration changes made in that menu go to the dashboard's Settings Audit Log rather than here, since that's where the rest of your config history lives.