Logging
Message, member, mod-action, voice and role logs — full audit history for your server.
Logging records everything that happens in your server into channels you choose. Once enabled it runs itself.
Setup
/logs config
Pick the channels for each log type. You can point every type at the same channel or split them by category (most servers use one channel per type). Configure from the dashboard too: Server → Settings → Logging.
Log types
| Type | Captures |
|---|---|
| Messages | Deleted & edited messages (with original content) |
| Members | Joins, leaves, nickname changes, avatar changes |
| Mod actions | Warns, timeouts, kicks, bans + who did them |
| Voice | Join/leave/move between voice channels |
| Roles | Role added / removed, role created / deleted |
| Channels | Channel created / deleted / renamed |
| Server | Guild name/icon changes, boost events, emoji changes |
| Security | Permission changes, role updates, anti-nuke events |
Searching logs
Use the search command to look through your server's log history:
/logs search <query>
This lets you find past events without scrolling through channels — useful for investigating incidents.
Log Server
If your server generates a lot of log traffic, you can route logs to a dedicated second server. The Log Server feature mirrors your log channels into another Discord server you control, keeping your main server clean.
Set this up from Server → Settings → Logging → Log Server on the dashboard.
Why bother
- Deleted-message forensics — nothing is truly "deleted" with message logs on
- Moderation accountability — every action attributed
- Raid detection — join spikes are obvious at a glance
Retention
Logs live in your Discord channels — they stay as long as the messages do. The bot's own database additionally stores command/mod logs for dashboard history.