Server Logging
DocsServer Setup

Server Logging

Route server events to one channel or split event types across channels.

How logging works

Appear stores an enabled state and a destination for each event type. You can route every event to one text channel or send different event families to different channels. Changing a route replaces only that event's destination.

Quick setup

  1. 1

    Route everything

    Omit the event name to point every supported event at one channel and enable logging.

    Command
    ,log add #logs
  2. 2

    Or split important events

    Run the add command once per event and destination.

    Command
    ,log add #message-logs messages
  3. 3

    Review the routes

    Confirm every event points to the intended channel and check whether logging is enabled.

    Command
    ,log list
logging

,log

Shows how to set up server logging, including how to route all events or a single event type to a channel and how to turn logging on or off.

,log
Open in command browser
logging

,log add

Routes a log event type to a channel and turns logging on. Leave the type off to send every type to that one channel. Setting a type again moves it to the new channel.

,log add <channel> [loggingEvent]
Example,log add #channel loggingevent
Arguments
channelRequired
loggingEventOptional
User permissionsManage Guild
Open in command browser
logging

,log list

Shows which channel each log event type is currently routed to and whether logging is enabled.

,log list
User permissionsManage Guild
Open in command browser

Supported event types

The source registry accepts voice, moderation, members, channels, roles, guild, messages, timeout, jail, invites, join, leave, reactions, polls, webhooks, soundboard, and emojis. Omit the event or use all to route everything.

ShortcutEquivalent route
logs messages #channellog add #channel messages
logs members #channellog add #channel members
logs roles #channellog add #channel roles
logs channels #channellog add #channel channels
logs voice #channellog add #channel voice

Pause, remove, or reset

Disable pauses delivery without deleting routes, so enable can resume the saved setup. Remove deletes one event route. Reset clears every route and returns logging to its default off state; it cannot be undone.

logging

,log disable

Stops all log events from being posted while keeping your configured routes saved, so `log enable` restores them.

,log disable
User permissionsManage Guild
Open in command browser
logging

,log enable

Resumes posting log events to the channels you already have configured.

,log enable
User permissionsManage Guild
Open in command browser
logging

,log remove

Stops routing one log event type so it is no longer posted anywhere. Other routes are left alone.

,log remove <loggingEvent>
Example,log remove loggingevent
Arguments
loggingEventRequired
User permissionsManage Guild
Open in command browser
logging

,log reset

Clears every logging route and returns logging to its default off state. Cannot be undone.

,log reset
User permissionsManage Guild
Open in command browser

Troubleshooting

  • Run log list and confirm logging is enabled and the event has a route.
  • Confirm Appear can View Channel, Send Messages, and Embed Links in the destination.
  • If a configured channel becomes inaccessible, Appear may disable that route instead of repeatedly failing to send.
  • Use the exact event names shown above; an invalid event is rejected without changing existing routes.