Visibility

Discord Logging Bot for Moderation, Security, and Audit Events

Security Bot posts moderation commands, anti-nuke warnings and punishments, and anti-raid locks to log channels in your own server. Premium adds an audit log channel and an AutoMod log channel. Your team sees what happened, who did it, and what the bot did.

  • Free: moderation and security log channels. Premium adds audit and AutoMod log channels.
  • Audit packs such as Moderation, Roles & Permissions, Channels & Threads, and Invites & Webhooks, with per-event toggles (Premium).
  • Logs are messages in your own Discord channels. They stay until deleted, and you decide who can read them.

Discord Logging Bot

Security Bot for Discord servers

Log channels
Mod, security, audit, AutoMod
Audit events
Packs with per-event toggles
Free tier
Mod + security logs

Last reviewed 2026-10-17

Logging coverage

Discord Logging Bot features

Moderation logs

Every ban, unban, softban, kick, mute, unmute, lock, and unlock via Security Bot, with moderator, target, reason, and duration. Anti-raid timeouts and locks, plus AutoMod and link filter punishments, show Security Bot as moderator. Not logged: /clear and /raid ban.

Security logs

User Warning: each counted anti-nuke action, with actions left before the limit. User Punished: anti-nuke or Beast Mode punishments. Anti Raid Lock: anti-raid channel locks. Verification: web check denials, possible alts, and raids Adaptive detects.

Audit and AutoMod logs

On Premium: Discord audit log events, grouped into packs you can toggle per event. Plus every AutoMod block and bot filter match, with the rule and matched content. Each goes to its own channel.

Why separate log channels matter

Discord's audit log is one long list with no notifications and no record of what a bot decided in response. When a nuke is stopped at 3 a.m., the team needs to know who was warned, who was punished, and for what. They need it in a channel they already watch.

Security Bot splits events by audience. Moderators watch the moderation log. Admins watch the security log. On Premium, whoever tunes AutoMod watches the AutoMod log, and the audit log channel mirrors Discord's own events for the packs you care about.

How logging works

Pick a channel for each log type on the Logging page. The moderation and security logs are available on every server.

On Premium, the audit log channel uses packs. A pack is a group of Discord audit events, such as moderation actions, role and permission changes, channel and thread changes, or invites and webhooks. Each event has its own toggle, so you can drop the noise.

Logs are ordinary messages that Security Bot posts in your channels. There is no separate log archive, retention period, or export. Entries stay until someone deletes them or the channel, and anyone who can see the channel can read them.

Reading the logs to tune protection

User Warning entries for staff during normal work mean a limit is too low or a role needs a whitelist entry. A punishment you did not expect means the same, or that an account needs a closer look.

The logs are the feedback loop for every other module.

Recommended log setup by server type

A small community on the free tier needs two channels, moderation and security. Both can live in one private category that only staff see. They are quiet on a small server, and every entry matters.

On Premium, add the AutoMod log even if you run only a few presets, because a silent block is impossible to tune. Enable only the audit log packs you will actually read, typically moderation, roles and permissions, and channels.

A public gaming server produces a busy moderation log, and that is the point. It shows every ban, softban, mute, and lock, with who did it and why.

Give moderators the moderation log, admins the security log, and whoever tunes filters the AutoMod log. Then nobody has to read everything to find their part. Turn on the audit packs for moderation, roles, and channels, and leave the rest off.

A network or a community past ten thousand members should split logs by audience and by server. Use the same channel layout in every server, so staff who work across them know where to look.

Name staff in each time zone who watch the security log. Pin a message in each staff channel saying which channel holds which events. Logs are messages in Discord and Security Bot has no export, so copy what you need for an incident review into your own notes.

Reading a security log entry

A typical anti-nuke sequence starts with one or more User Warning entries for an action such as channel delete. Each shows how many actions remain before the limit. Then comes User Punished, with the punishment you chose. Each entry names the account involved.

Read them together and you know what happened and what the bot did, before you open Discord's audit log to see which channels are gone.

If the account is a staff member doing ordinary work, the fix is a higher limit or a per-action whitelist entry. If it is not, the punishment already stopped them, and you move to the recovery runbook.

Anti-raid writes one Anti Raid Lock entry to the security log when it locks the channels on your lock list. Its timeouts and each channel lock also appear in the moderation log, with Security Bot as the moderator and Anti Raid as the reason.

Anti-raid bans are not logged, so check Discord's audit log for those. Anti-spam announces its locks in the locked channel instead of the log. The free invite link filter deletes invites without logging them.

Beast Mode writes no entry when it activates or ends. It only writes User Punished for each punishment while it is active.

What Discord's audit log gives you and what the log channels add

Discord's audit log records who changed what for 45 days. Anyone with the View Audit Log permission can see it. It is one list with no notifications and no filter beyond user and action type.

It does not know that a bot responded, cannot be routed to a channel, and expires on Discord's schedule rather than yours. It is still the authoritative record of native actions. Open it first after an incident, because it shows every deletion, not only the ones a bot reacted to.

The log channels add the layer Discord does not have. The security log records the bot's warnings and punishments next to the account that caused them.

On Premium, the audit log channel mirrors the native events you choose into a channel where staff get a notification. The AutoMod log shows the matched content next to the bot action that followed.

Security Bot reads message content in real time for its filters. When a filter matches, that content appears in the log entry in your own channel.

A maintenance routine for logs

Weekly, read the security log top to bottom. On Premium, an AutoMod log full of one rule blocking the same harmless phrase means an allowed term is missing.

Monthly, open the Logging page and confirm each channel is still assigned and still private. Log channels get deleted during cleanups or made visible during a permission reshuffle. A log nobody can read is the same as no log. Trim audit packs that nobody has looked at since the last review.

After any incident, copy the relevant entries into your incident notes, since log messages disappear if the channel is deleted.

Setup

How to set up Discord Logging Bot

Steps that list a command can also be done in Discord. On Premium, settings commands such as /setlimit and /whitelist reply with a dashboard link instead.

  1. Step 1: Create the log channels

    Make private channels for the moderation and security logs, plus audit and AutoMod logs on Premium. Make each one visible only to the staff who need it.

  2. Step 2: Open Logging under Settings

    Assign a channel to each log type. On the free tier, /logs mod and /logs security work too.

  3. Step 3: Choose audit log packs

    On Premium, enable the packs you want mirrored from Discord's audit log and toggle individual events off if they are noisy.

  4. Step 4: Save and test

    Run a harmless moderation command, such as a one-minute /mute, and confirm it appears in the moderation log.

Questions

Discord Logging Bot FAQ

Common questions about Discord Logging Bot use cases, coverage, and setup.

What does Security Bot log?

Moderation log: moderation commands except /clear and /raid ban, plus anti-raid timeouts and locks and the bot's punishments after AutoMod hits. Security log: anti-nuke warnings, anti-nuke and Beast Mode punishments, and anti-raid locks. On Premium, Discord audit log packs and AutoMod hits go to their own channels.

How long are logs kept?

Logs are messages in your own Discord channels, so they stay until someone deletes them or the channel. Security Bot has no retention tiers and no log export.

Can I log only some audit events?

Yes, on Premium. Audit log packs have per-event toggles.

Are logs required for anti-nuke to work?

No. But without a security log channel you will not see warnings or punishments. Only the server owner's DM records each punishment.

Should log channels be private?

Yes. Make each one visible only to the staff who need it. Security and audit logs show who was punished and why, which is not information for the whole server.

Does the audit log channel replace Discord's audit log?

No. It mirrors the packs you choose into a channel where staff get notifications. Discord's own audit log stays the authoritative record of native actions.

Logging

Ready to protect your Discord server with Security Bot?

Add Security Bot to your server to get started with Discord Logging Bot. Anti-raid, anti-spam, and the other Premium modules run on a separate bot; the Premium page explains how to add it.