Logging System
Record what happens on your Fluxer server: messages, members, roles, channels, voice activity and moderator actions, each in its own channel.
Topics: logs, logging, audit, events, tracking
Track everything that happens in your server with 55 event types organized into 18 categories, per-category channel routing, and custom embed colors — all configured from the dashboard.
Overview
The logging system records server events and posts detailed embeds to the channels you choose. It is the backbone for moderation accountability and general visibility: who joined, what was deleted, which roles changed, who was banned, and much more.
Everything is configured from Dashboard → Logs. Nothing is enabled by default — you decide exactly which categories to track and where each one is sent. For a one-command shortcut that turns everything on in a single channel, see the Logs commands.
Enabling and basic setup
- Open Dashboard → Logs for your server.
- Toggle Active in the page header to switch the system on.
- Use the All log channel picker in the header to send *every* category to one channel — the quickest way to get started.
- Or expand any category below to give it its own channel and toggle it on.
Tip: Netrcol needs View Channel, Send Messages, Embed Links, and Read Message History in each channel you log to. The setup health check on the page will warn you if a permission is missing.
Per-category channels
Each category is an expandable row with its own channel picker and on/off toggle. This lets you split your logs across channels — for example moderation logs in a private staff channel, and join/leave logs in a public one.
If every category points at the same channel, the header All log channel picker shows that channel; if they differ, it shows *“Channels differ.”* Setting it again re-points everything to a single channel.
Embed colors
Every event has a color stripe you can customize. Open a category, and each event row has a color swatch — handy for telling categories apart at a glance (for example red for moderation, green for joins).
Log categories
Netrcol groups its 55 event types into these 18 categories:
| Category | What it logs |
|---|---|
| Bot | Bot interaction and guild lifecycle logs |
| Moderation | Ban, unban, automod, and staff action logs |
| Message | Readable message delete, edit, and bulk-delete logs |
| Reaction | Emoji add and remove activity |
| Member | Joins, departures, role updates, nickname changes, and timeouts |
| Channel | Channel create, delete, rename, topic, and category changes |
| Role | Role create, update, and delete logs |
| Voice | Voice state changes (debug voice events require an opt-in flag) |
| Invite | Invite create and delete logs |
| Server | Server settings, name, and structure changes |
| Asset | Emoji and sticker update logs |
| Webhook | Webhook update events |
| Security | Risky activity and protection-system logs |
| Integration | Guild integration update events |
| Scheduled Event | Scheduled event create, update, and delete logs |
| Pinned Message | Channel pin update logs |
| Presence | Typing and presence logs (opt-in, high volume) |
| User | User profile changes, shown once per affected guild |
Smart titles
Some categories use cleaner, more specific titles instead of a generic “Updated.” Member departures, for example, try to separate left, kicked, and banned; single-field channel changes use a precise title like “Channel Topic Changed” rather than “Channel Updated.”
Audit-aware enrichment
When server audit logs are available, Moderation and Member logs are enriched with the actor and the audit reason — so a ban log can show *who* issued it and *why*, not just that it happened.
Quick setup from chat
If you just want everything in one channel without opening the dashboard:
!logs-setup 123456789012345678This enables all 18 categories and points them at that channel. Turn the whole system off with:
!logs-disableFull details are on the Logs commands page.
Notes & tips
- Nothing is on by default. You choose which categories to track — start small and add more as needed.
- High-volume categories. *Presence* (typing/presence) is disabled by default and best left off unless you're debugging; it also requires a bot-environment flag to emit anything.
- Debug voice events stay silent unless a global opt-in flag is enabled in the bot environment.
- Deduplicated user logs. A single profile change is grouped per guild, even if several cached messages match that user, so you won't get duplicate entries.
- Message cache. To show deleted/edited content, Netrcol keeps a short in-memory cache of recent messages per server. It is never written to permanent storage — see the Privacy Policy.
Next steps
- Configure it on Dashboard → Logs
- Review the Logs commands
- Make sure Netrcol has the right permissions