Iris
Add to Discord

Logging

Log server events to a dedicated channel.

Configure Logging in the dashboard

Overview#

Logging writes down what happens in your server. 38 event types across 12 groups, from a deleted message to a renamed emoji, each one an embed in your log channel with who did it and what changed.

Where Discord tells it who was responsible, Iris reads the audit log and names them. A ban, a kick, a role change or a channel edit arrives with the moderator attached rather than as an anonymous event.

The channel set here is also the fallback for the whole bot: every module logs here unless it has a log channel of its own.

Setup#

  1. Make a private channel your moderators can read and nobody else can.
  2. Open the dashboard and go to Moderation > Logging, then turn the module on.
  3. Set the Default Log Channel.
  4. Press Enable All under Events, then turn off the groups you do not want.
  5. Add anything noisy or private under Ignored Channels, then save.

Settings#

SettingTypeDefaultWhat it does
Enable LoggingToggleOffThe master switch. Nothing is recorded while it is off.
Default Log ChannelChannelNoneWhere events are posted, and the fallback log channel for every other module.
Ignored channels and categoriesChannelsNoneActivity here is never logged. Picking a category ignores every channel inside it.
EventsTogglesVariesOne switch per event type, grouped. Enable All and Disable All set them in one press.

Event groups#

GroupCovers
Message EventsDeletes, edits, image deletes and bulk deletes
Member EventsJoins, leaves, bans, unbans, kicks, mutes, warns, timeouts and profile updates
Role EventsRoles created, deleted and edited
Channel EventsChannels created, deleted and edited
Voice EventsMembers joining, leaving and moving between voice channels
Server EventsServer settings changed
Invite EventsInvites created, deleted, and invites posted in chat
Emoji EventsEmojis added, removed and renamed
Moderation EventsModerator commands as they are run
Thread EventsThreads created, deleted and edited
Webhook EventsWebhooks created, deleted and edited
Stage EventsStage channels created, deleted and edited

Commands#

CommandWhat it doesRequires
.logging helpThe log channel and the per-event toggles from chat.Manage Server

Permissions#

PermissionWhy Iris needs it
View ChannelsSees the channels events happen in, and the log channel.
Send MessagesPosts each log entry.
Embed LinksEvery entry is an embed.
View Audit LogNames the moderator behind a ban, kick, role change or channel edit. Without it those entries say who was affected but not who acted.
Read Message HistoryShows the old text of an edited or deleted message.

What it looks like#

I
Iris APP Today at 8:53 PM
Message deleted

In #general

Author

@member

Deleted by

@moderator

Content

join my server discord.gg/example

I
Iris APP Today at 8:53 PM
Member banned
Member

@rulebreaker

Moderator

@moderator

Reason

Advertising

A message delete and a ban, as they arrive in the log channel.

Tips and gotchas#

Entries say who was affected but not who did it.

Iris is missing View Audit Log. That permission is the only source for the responsible moderator.

The log is too busy.

Turn off Voice Events and Message Edit first. They are the two that dominate an active server.

Can different events go to different channels?

Not from this page. Modules with their own log channel, such as AutoMod and tickets, can be split off that way.

How is this different from the log viewer?

Log Viewer shows recent message and member events in the dashboard. This module is the permanent record in Discord.