Server Logs
Server Logs tracks everything that happens in your server and records it — both as formatted embeds in Discord and as searchable entries in the panel.
Everything is configured from the panel. There is nothing to set up with slash commands.
📋 What gets logged
Server Logs is split into 10 independent categories. You enable only the ones you want.
| Category | What's tracked |
|---|---|
| 👥 Members | Joins, leaves, bans, unbans, kicks, nickname changes, role changes |
| 💬 Messages | Edits, deletes, bulk deletes, pins |
| 📁 Channels | Create, delete, rename, topic and permission changes |
| 🎭 Roles | Create, delete, rename, permission and color changes |
| 🎙️ Voice | Join, leave, move between channels, deafen, mute, stream start/end |
| 🏠 Server | Name, icon, verification level, AFK channel changes |
| 🔗 Invites | Create and delete, with full invite metadata |
| 😀 Emojis | Create, delete, rename |
| 🤖 Bots | Bot added to the server |
| 🔨 Moderation | Ban, kick, warn, mute, softban, unban, unmute |
📡 Log channels
Each category can be enabled independently and assigned its own dedicated log channel.
You can also set a single global log channel as a catch-all fallback. If a category has no channel of its own, its events go to the global channel.
Example: send moderation events to a private
#mod-logand everything else to a general#server-log.
🙈 Ignore rules
To reduce noise, you can exclude events from logging:
- Channels — events in ignored channels are never logged (useful for bot spam or private staff channels).
- Roles — members holding any ignored role are excluded from logging.
- Users — specific Discord user IDs are excluded.
🔎 Log viewer
Stored events can be browsed directly in the panel from the Viewer tab.
You can filter by:
- Category (members, messages, roles, etc.)
- Keyword (across event type, actor, and target)
- Actor ID / Target ID
- Date range (from / to)
Results are paginated, and you can export the current filtered view as a JSON file.
Storage is enabled by default. Retention is 30 days by default and can be configured up to 365 days.
🔗 Server Logs and Moderation
When the Moderation feature is active, moderation actions (bans, kicks, warns, mutes, and their reversal) flow automatically into the Moderation log category — no extra setup needed.
The moderation category card shows a status badge:
- Bridge connected — the Moderation feature is enabled and actions are auto-synced.
- Standalone — the moderation category only logs what Discord's audit log reports.
🔗 Server Logs and other features
Other features that take moderation actions also feed the Moderation category, so everything lands in one place:
- Automod and Anti-Raid actions.
- Honeypot triggers. When Server Logs has a Moderation channel configured, the Honeypot's own log channel is bypassed to avoid duplicate entries.
👍 Recommended setup
- Set a global log channel as a fallback.
- Enable the categories you care about and give the sensitive ones (moderation, members) their own private channels.
- Add ignored channels for bot spam or noisy integrations.
- Keep storage on so you can search history later.
💡 Best practices
- Send moderation logs to a staff-only channel.
- Avoid logging every category at once on very large servers — pick what you actually review.
- Use the Viewer's export to keep records beyond the retention window.
- Combine with the Moderation feature so manual and automatic actions are all captured.