Logging
Logging sends a durable audit stream of server events to channels you choose—joins, leaves, message edits and deletes, moderation actions, and other core events supported on your tier.
What it does#
Instead of guessing who deleted a message or when someone joined, staff read structured log entries in dedicated channels. Each event type can route to the same or different log channels depending on noise level.
Retention and event breadth depend on tier: Free includes short retention and core events; Pro adds longer retention, bulk-delete archives, voice activity logs, and more destinations.
Dashboard path#
Dashboard → Servers → {Guild} → Logging
Enable logging, map event categories to channels, and tune which details appear (attachments, embeds, before/after content). Start with member and moderation logs, then add message logs if moderators want full visibility.
Key settings#
| Setting | Free | Pro |
|---|---|---|
| Log retention | 7 days | Longer on Pro |
| Log channels | Up to 2 | More channels |
| Member join/leave | Yes | Yes |
| Message edit/delete | Core set | Extended + bulk delete archive |
| Voice events | No | Yes on Pro |
Restrict log channels to staff roles—logs often contain sensitive metadata.
Related features#
- Moderation — cases vs raw event stream
- Automod — automod actions can appear in logs
- Tickets — separate from ticket transcripts; use both for support audit
- Anti-raid — join and lockdown events worth logging
Channel strategy#
Many teams run #member-log for joins/leaves and #mod-log for bans, automod, and message deletes—within the Free limit of 2 log channels. Prioritize events you actually review; noisy logs get ignored.
Message delete logs can include content snippets. Treat log channels as confidential—only staff roles should read them. Retention on Free is 7 days; export manually if your community policy requires longer audit history until you upgrade.