Event logging
Privacy-bounded Discord and configuration timelines.
Start here
Send events to the correct channel and find a failed delivery
PulseOne → Dashboard → select your server → Modules → Event logging
Choose the server → Modules → Event logging.
In Routing and retention open Destinations, add the Discord channel you use for logs and keep Destination enabled on.
Open Routes, select the event categories and choose the destination; turn on Route enabled. Decide whether bot actors should be included.
Under Privacy posture decide which fields to redact; under Retention set the number of days you want to keep events and deliveries.
Save the policy and trigger a harmless test event. Return to Search retained events, filter the category, and inspect Event detail and Delivery outcomes.
Practical example
Route moderation actions to a staff-only logging channel and set a short retention period. Test one authorized action before relying on it for incidents.
Before you begin
- No module dependency listed.
- Discord bot permissions for the operational slice: ViewAuditLog, ViewChannel, SendMessages, EmbedLinks.
- Review staff roles and channel access in your server before using the feature.
Overview of the setup
Before you begin
Decide which Discord events and configuration changes need an audit trail, and choose staff-only destination channels.
Configure
Set routes and retention windows with minimal message content. Test an ordinary event and a permission/configuration change.
Test and verify
Use the searchable timeline and delivery status to ensure records reach the chosen destination without exposing private content.
Features explained
What each feature does and what to check before publishing or installing the result.
Discord event routes
Route only the event classes your staff will act on; separate sensitive operations from general activity channels.
Configuration history
Configuration events make administrative changes traceable independently of message logs.
Searchable delivery outcomes
Review delivery outcomes and retry health to distinguish a missing event from a channel permission failure.
If it still does not work
- No events listed? Check Routes, destination permissions and the time/category filters.
- A record without delivery is not necessarily a missing event; inspect Delivery outcomes to identify which destination failed.
Troubleshooting and safety checks
- Missing entries? Check selected event types, retention, bot channel access and destination health.
- If a capability is unavailable in the UI, check the module's current rollout/availability instead of assuming every roadmap item is live.