Free Discord Logging Bot: What to Log and Why
Published 25 Oct 2026
Also available in: Français · Português · Español · Deutsch
Logs are the part of server management nobody thinks about until they need them. Someone claims a moderator insulted them, a message with a scam link vanishes before anyone screenshots it, or a channel disappears overnight. Without logs, you are left with memories and accusations. With logs, you have a timeline.
This guide covers what is worth logging, how to organise it so staff actually read it, and the privacy side that many servers forget.
Discord's audit log is not enough on its own
Discord has a built-in audit log under Server Settings. It is useful: it shows who banned whom, who changed a role, who edited a channel. But it was designed for administrative actions, not for conversation. It does not keep the content of deleted or edited messages, it is only visible to people with the View Audit Log permission, and it is awkward to search during a busy incident.
A logging bot fills those gaps by posting events in channels you choose, with the details your staff need at a glance.
The five categories worth logging
MagnificBot's Logging module, included in the free plan, groups events into five categories. Each one can be switched on or off and sent to its own channel.
| Category | What it records | Why it helps |
|---|---|---|
| Messages | Deleted messages (with their text) and edits (before and after) | Settles "I never said that", catches scam links that were deleted |
| Members | Joins and leaves, nickname changes, role changes | Spots raids, alt waves and impersonation via nicknames |
| Moderation | Bans, unbans and timeouts, including ones done by hand in Discord | Keeps moderators accountable |
| Server | Channels and roles created or deleted | Detects mistakes and compromised staff accounts |
| Voice | Joins, leaves and moves between voice channels | Resolves voice harassment reports |
Voice logging is off by default because it is noisy on active servers. Turn it on if voice reports are common in your community.
A log layout staff will actually read
One giant #logs channel turns into wallpaper. A small set of focused channels works better:
- #log-messages: deletions and edits. The busiest channel; skim it when a report comes in.
- #log-members: joins, leaves and role changes. Watch it during raids.
- #log-moderation: every sanction. This is the one to review weekly.
- #log-server: structural changes. Should be quiet; anything unexpected here deserves attention.
Put them in a category that only staff can see, and give most moderators read-only access. Logs that anyone can edit or delete are not evidence.
Ignore the noisy channels
Some channels generate useless logs: a bot-commands channel, a counting game, a staff chat where deletions are routine. Add them to the ignored channels list so the logs stay readable.
More than Discord channels: the dashboard view
Every event is also stored in the dashboard's Events tab, so you can look things up even if a log channel was deleted or never configured. Events are kept for 90 days there. A separate Audit tab records changes made in the dashboard itself: who edited a module, who changed a setting. If several people manage the bot, this is how you find out who switched AutoMod off at 2 a.m.
Dashboard access roles let you give a moderator or support member read access to logs without handing them broad Discord permissions.
A note on edited messages
Discord only tells bots the old text of an edited message if the bot had that message in memory. For recent messages this usually works; for very old ones the "before" may show as unknown. This is a platform limitation that affects every logging bot.
Privacy: log responsibly
Message logs store what people wrote, including things they chose to delete. That deserves some care:
- Say it in your rules. A single line such as "Messages, including deleted ones, are logged for moderation" is honest and discourages abuse.
- Limit who can read message logs. Not every helper needs to see deleted content.
- Use logs for moderation only. Do not quote deleted messages publicly or use them to embarrass people.
- Do not log what you do not need. If voice logs never help you, leave them off.
- Delete old log messages in Discord if you have no reason to keep them; the dashboard copy expires on its own.
If you are combining logging with other moderation tools, see how it fits alongside the rest of your stack in our MEE6 vs Dyno vs Carl-bot vs MagnificBot comparison.
FAQ
Does the bot log direct messages?
No. It only logs events that happen inside your server.
Are bans done through Discord's own menu logged?
Yes. Bans, unbans and timeouts are detected even when a moderator does them by hand, and they are also recorded as moderation cases.
Can I send all categories to one channel?
Yes. You choose the channel for each category, and nothing stops you from using the same one. Separate channels are just easier to read.
Is logging limited on the free plan?
No. All five categories, ignored channels and the dashboard history are included. Premium mainly removes the promotional messages and raises limits in other modules; see pricing.
Set up your log channels in a few minutes on app.magnificbot.com, before the day you need them.
Try MagnificBot for free
All modules included, configured from a web dashboard. No credit card, no time limit.
Add to Discord — it’s free