Discord logs and activity journal

In pictures

Enlarge

Log events and destinationsOriginal image

See 1 more screenshot

Enlarge

Server event journalOriginal image

Step by step

1. 1

   In Logs → Discord events, enable the module and create a named rule.

2. 2

   Open Events to select triggers, then Destination to choose the channel. Configure exclusions and the message appearance in the same rule.

3. 3

   Save changes, enable the rule and use Send a test. Existing settings are automatically represented as rules; an event produces at most one message per channel.

4. 4

   Configure decision notifications separately in Moderation logs as needed.

5. 5

   Use the Journal to find collected events, even when Discord delivery is disabled.

Permissions and content

Spider needs View Channel, Send Messages and Embed Links for embeds. Member and content events depend on data available to the bot. Uncached or unreceived data remains unavailable and is not invented in logs.

Exceptions and notifications

Role exclusions concern roles or members involved in the event. They do not grant staff extra access. Log channels should be limited to people who need their contents.

Journal retention

The Journal shows events retained by Spider within bounded retention, not the entire Discord history. Use available exports and cases for follow-up while respecting your permissions.

Practical example