Logging

Route Discord and QREATE business events into one or more log channels.

Set it up

1. 1Open Logging and enable it.
2. 2Create routes for event categories or specific events.
3. 3Use Preview or Test Log to confirm embeds before relying on them.

Route strategy

• Use one critical moderation log for bans, kicks, timeouts, purges, and lockdowns.
• Use separate noisy logs for message edits/deletes, voice, and automation events.
• Use Test Log before relying on a route in production.

Known shape

Logging combines Discord-native events and QREATE business events. Some module actions produce richer logs than Discord audit logs because QREATE knows the module context.

Example routes

#mod-log:
memberBan, memberKick, timeout, purge, lockdown, warnings

#audit-log:
messageDelete, messageEdit, roleUpdate, channelUpdate

#automation-log:
automationRoleGranted, verificationPassed, achievementUnlocked

What to know

• Logging has a large event catalog; route only what staff will read.
• Some business modules emit richer events than Discord audit logs.
• A member-leave entry also shows when they joined, how long they stayed, and the roles they held on the way out. Discord discards all of that the moment someone leaves, so the log entry is the only place left to read it.