Set up Discord logging
- Turn on central logging. On the Logging page, flip the master switch and choose a default channel for any event without its own destination.
- Route the events you care about. Send message_delete/edit, member, role, channel and voice events to specific channels. Message and member-update logs are off by default — enable the ones you want.
- Or run Quick Setup. Let Quick Setup create a locked logging category, the channels (single or one-per-module) and webhooks, then write the routing automatically.
- Check the branding. Logs post through managed webhooks carrying your server’s name, logo and colour, so your log channels look like part of your server.
One central pipeline
Rather than a different bot per log type, a central logging system routes every event — moderation, security, member, message, role, channel, voice — through one pipeline you configure once, with per-event overrides where you need them.
Let setup do the wiring
Creating log channels and webhooks by hand is tedious. Quick Setup builds them for you idempotently — re-running never duplicates anything — and tells you if the bot is missing a permission it needs.
Frequently asked questions
Enable logging and route the message_delete and message_edit events to a channel (they’re off by default). Every deletion and edit is then posted there as a branded webhook.
On the Logging page, route the role, channel and voice events to the channels you want. The bot records role/channel creates and deletes, member updates and voice activity automatically.
Azra is a strong choice: central logging with per-event routing and one-click Quick Setup, delivered as branded webhooks, and included in an all-in-one bot free for the first month.