Logging - Hedwig

Logging gives staff a dedicated record of events that are difficult to reconstruct later. Hedwig stores five log destinations: message, member, moderation, voice, and server events. Use private channels or the automatic private Hedwig Logs category.

Commands

Command	Use it to
`/logging setup`	Choose and configure log channels
`/logging enable`	Enable event logging
`/logging disable`	Pause event logging
`/logging reset`	Remove the logging configuration

What each channel receives

Destination	Examples
Message logs	Message edits, deletes, and bulk deletes
Member logs	Joins, leaves, kicks, role changes, and nickname changes
Moderation logs	Bans, unbans, and timeouts
Voice logs	Voice joins, leaves, moves, and state changes
Server logs	Channel, role, emoji, sticker, and server-setting changes

Setup checklist

Create staff-only log channels, or let Hedwig create the Hedwig Logs category automatically.
Give Hedwig permission to view and send messages there. Automatic setup also needs Manage Channels; webhook-backed delivery needs Manage Webhooks.
Run /logging setup.
Trigger a harmless test event.
Confirm the event appears before enabling antinuke or automod.

Logging is useful only when staff can access it. Keep the channels private, but make sure the on-call moderation team can read them during an incident.

⌘I