Logging System
Set up logging to track message deletions, member changes, moderation actions, and channel updates with per-event channel routing.
Overview
Nevi's logging system lets you route different server events to different channels. Unlike bots that dump everything into one log channel, Nevi gives you per-event channel routing. Send moderation logs to one channel, member joins to another, and message deletions to a third.
Each event can be independently enabled or disabled, and you can route multiple events to the same channel if you prefer a simpler setup.
Setting up logging
To start logging an event, use the /log set command with the event name and the channel where you want logs sent.
Usage
/log set <event> #channel
Example
/log set messageDelete #message-logs
Nevi needs Send Messages and Embed Links permissions in the target channel. It's recommended to restrict these log channels so only staff can view them.
Viewing your log configuration
Check which events are currently being logged and where they're routed.
Usage
/log view
This shows a list of all events with their assigned channels. Events without a channel assigned are not being logged.
Removing a log event
To stop logging a specific event, remove its channel assignment.
Usage
/log remove <event> #channel
Example
/log remove memberLeave #member-logs
Setting an entire category
Instead of setting each event one at a time, you can assign a whole category of events to a single channel with one command.
Usage
/log category <category>
Example
/log category moderation
This sets every event in that category to the specified channel. You can still override individual events afterward.
Message Events
messageDelete- a message was deletedmessageEdit- a message was edited (shows before/after)messageBulkDelete- multiple messages purged at once
Member Events
memberJoin- a new member joined the servermemberLeave- a member left or was removedmemberUpdate- a member's roles changedmemberNickname- a member changed their nicknamememberAvatar- a member changed their avatarmemberUsername- a member changed their username
Moderation Events
ban- a member was bannedunban- a member was unbannedkick- a member was kickedmute- a member was mutedunmute- a member was unmutedwarn- a member was warned
Other Events
channelCreate- a channel was createdchannelDelete- a channel was deletedroleCreate- a role was createdroleDelete- a role was deleted
Detailed logging
By default, when a message is deleted, Nevi can only log the content if the message was still in Discord's cache. Older messages may show as "unknown content" in your logs.
Detailed logging solves this by having Nevi store message content so that deleted and edited messages always show their full original text.
Usage
/config detailedLogging true— Enable detailed logging
With detailed logging enabled, your message delete and edit logs will include the full before/after message content regardless of how old the message was. This is especially useful for catching users who delete rule-breaking messages.
Best practices
A well-organized logging setup makes moderation much easier. Here are some recommendations:
Separate your channels
Use different channels for different log types. A common setup is #mod-logs for moderation events (bans, kicks, warns), #message-logs for message deletions and edits, and #member-logs for joins, leaves, and member updates.
Restrict access
Log channels should only be visible to your moderation team. Set channel permissions so regular members can't see deleted message content or moderation actions.
Enable detailed logging
If you care about message delete/edit logs being complete, always turn on detailedLogging. Without it, you may miss context on deleted messages that were already out of cache.
Related Commands
/logmanagementRequires adminConfigure logging channels for server events
/configmanagementRequires adminConfigure server settings