Native Discord Event Logging
Choose private Discord destinations for supported events, then check delivery and attribution.
- Audience
- team lead · server admin
- Availability
- feature flagged
- Maturity
- beta · partial
Last reviewed
On this page
Confirm the deployed logging version
Route from broad defaults to narrow overrides
Choose a private destination
Select a staff-only Discord channel where the bot can view the channel, send messages, and embed links or content.
Check: Only intended moderation or audit staff can read the resulting event messages.
Set the broad route
Configure the global or category route first, then add event overrides only where a different destination or disabled state is required.
Check: Each event resolves through event, category, and global inheritance without accidental public delivery.
Review sensitive defaults
Inspect message content, poll votes, voice presence, invites, topics, AutoMod content, audit actors, high-volume events, and ignore-list choices before enabling them.
Check: Sensitive or high-noise collection is deliberate, minimal, and consistent with server notice and policy.
Verify one delivery
Wait for the auto-save result, send the supported test event, and check destination, attribution, formatting, and delivery health.
Check: The selected route is saved and one representative event arrives without widening access.
Where event logging can fall short
| Limit | Effect |
|---|---|
| Gateway intents and cache | An event or prior state may be unavailable to render. |
| Discord audit logs | Actor attribution is delayed, missing, or best effort and requires audit-log access. |
| Embed limits | Long values or content can be truncated. |
| Outbox and retry | A stored delivery payload and error state can remain even when the Discord message fails. |
| Disable or ignore | Stops future delivery; it does not erase existing Discord messages, exports, or retained audit/outbox copies. |
A route shows no channels or delivery fails
What you see: The selector is empty, a test fails, or events remain unhealthy.
What may be happening: The deployed channel provider, server context, Discord authorization, bot membership, destination permissions, API availability, or delivery worker may be unavailable.
What to do
- Confirm the selected server and that the deployed dashboard is using its intended Discord channel provider.
- Verify bot membership and view, send, and embed access in the exact destination.
- Retry channel loading once, inspect delivery health, and avoid repeated route changes while an error remains.
- Escalate with the server ID, destination ID, event name, and error time—never with a bot token.