Skip to content

Server Logging

Track important server activity with the /logging command group. Logging is powered by reported events in the Discord API, and then displays them in the designated channels. Moderation activities taken with Armory Bot are also captured and displayed in dashboard.

Overview

The logging system supports category-based event tracking for:

  • Member events
  • Message events
  • Role and channel changes
  • Voice activity

You can route server, message, voice, and moderation logs to separate channels.

Permissions

Logging configuration commands require logging/admin permissions in your server.

Quick Setup

1) Configure channels

/logging setup server_channel:#server-logs message_channel:#message-logs voice_channel:#voice-logs mod_channel:#mod-logs

You can provide one channel or multiple channels in the same command.

2) Enable event categories

/logging toggle event_type:message_delete enabled:true
/logging toggle event_type:message_edit enabled:true
/logging toggle event_type:member_join enabled:true
/logging toggle event_type:member_leave enabled:true

3) Review configuration

/logging view

Command Reference

/logging setup [server_channel] [message_channel] [voice_channel] [mod_channel]

Set destination channels for each logging stream.

/logging toggle <event_type> <enabled>

Enable or disable a logging category.

Supported event_type values:

  • member_join
  • member_leave
  • member_update
  • message_delete
  • message_edit
  • role_changes
  • channel_changes
  • voice

/logging ignore <channel>

Exclude a text channel from message edit/delete logging.

/logging unignore <channel>

Remove a channel from the ignore list.

/logging view

Display configured channels, active toggles, and ignored channels.

Practical Event Coverage

Each toggle controls a family of logs. For example:

  • member_update can include nickname/role/profile changes
  • role_changes covers role create/update/delete style events
  • channel_changes covers channel create/update/delete style events
  • voice covers joins, leaves, moves, and mute/deafen-style updates

Exact emitted embeds depend on what Discord provides for each event at runtime.

Best Practices

  1. Use separate channels for message logs and moderation logs.
  2. Start with message delete/edit + member join/leave, then expand.
  3. Ignore spam-heavy channels to keep logs actionable.
  4. Run /logging view after changes to verify your setup.

Troubleshooting

No logs are appearing

Check:

  1. Log channels are configured with /logging setup.
  2. Event categories are enabled with /logging toggle.
  3. The source channel is not ignored.
  4. The bot can view/send/embed in your log channels.

Some events are missing details

Discord may not always provide full cached message/member context for every event. This is expected on certain uncached events.