Documentation

Start with General Logs

In Manage Servers, open Logging and select a General Logs channel. Enable only the event types your server needs. Without separate destinations, enabled command and server audit entries go to General Logs.

Choose what to record

Command Audits cover slash commands, with a separate switch for moderation commands. Message Events cover edits, deletes, image attachments in deleted messages, bulk deletes, invites, and purge transcripts. Member Events have separate switches for joins, leaves, role additions and removals, timeouts, nicknames, bans, and unbans. Role, channel, emoji, and voice events each have their own switches. Image, invite, emoji, and voice logs start off until you enable them.

Split destinations

Turn on Specify Channels For Each Log Type to route each event to its own channel. Moderation, utility, and community commands can also have separate command logs. Empty choices fall back to General Logs. Turn the split option off and save to clear those separate destinations. /status is a general command, not a moderation action.

Exclusions

Add Ignored Channels to skip message, invite, channel, or voice events from those channels. Ignored Roles For Deleted Messages prevents deletion logs for those members when Central can still identify their roles. Some uncached messages have no author role information, so the role exclusion cannot always be applied.

Module-specific logs

Moderation action logs use the Moderation Logs channel in Moderation. Ticket transcripts and ticket activity use the Ticket Log Channel in Tickets. Application submissions go to each application's Review Channel. These are separate from General Logs.

If a log is missing

Check that the Logging module and event type are enabled, the channel is saved, and Central can View Channel, Send Messages, and Embed Links there. Bulk-delete and purge transcripts also need Attach Files. Some details are unavailable when Discord did not cache the original message or Central cannot read the audit log.