Skip to main content
seize’s logging system captures dozens of server events and sends them to the channels you choose. You can route events individually, assign custom accent colors, and ignore specific members or channels so your log feeds stay clean.

​
Enable logging

1

Turn logging on

Run ,log enable to globally enable the system using any existing configuration.
2

Bulk-configure with a channel

Run ,log enable #logs --default to route the default event set to a channel. Run ,log enable #logs --all to route every supported event to a channel.
If you want to exclude voice events during bulk setup, use ,log channel #logs exclude:voice_join,voice_leave.

​
Manage events per channel

  • Add a single event: ,log add #mod-logs message_delete
  • Remove a single event: ,log remove #mod-logs message_delete
  • Route all events to a channel: ,log channel #logs
  • List valid events: ,log events

​
Supported events

​
Customize log colors

You can set a custom hex color for any event in a specific channel.
  • Set a color: ,log color set #mod-logs message_delete FF0000
  • Remove a color: ,log color remove #mod-logs message_delete
  • List colors: ,log color list #mod-logs
If no custom color is set, seize uses its default primary accent.

​
Ignore members and channels

Some members or channels generate noise. You can exclude them from all logging.
  • Ignore a member: ,log ignore @user
  • Ignore a channel: ,log ignore #spam
  • Stop ignoring: ,log ignore remove @user
  • List ignored entities: ,log ignore list

​
Disable logging globally

Run ,log disable to stop sending logs without deleting your configuration. Run ,log enable again to resume exactly where you left off.
For best results, create a dedicated logging webhook channel and grant seize the Manage Webhooks permission. seize will automatically create and reuse a webhook named “Seize Logging” for clean, branded log posts.