Logs keep track of what happens in your community: deleted or edited messages, joins and leaves, sanctions, channel and role changes, anti-raid actions… The texts, categories and settings are those of the Discord version. Everything is set on the dashboard's Logs settings page.
How logs work
- One channel per category, one switch per log. A log is posted if its category's channel is set and it isn't turned off. Everything is on by default.
- Filters per category: ignore bots, some channels or some roles.
- Community language. Every log is written in the community language.
- Format. Each log is a box: a title, one line per piece of information ("Member", "Channel", "Reason"…) and the event's date.
- Who did it. To show the author of an action (who deleted this channel, who banned this member…), the bot reads Fluxer's activity log: it needs the View activity log permission.
- No mentions: logs show members without notifying them, except the emergency mentions of critical logs.
Picking the log channels
On the Logs settings page, each category has its card: the destination channel (or + to have the bot create a private channel), one switch per log and filters. The page only shows the logs the Fluxer bot posts.
| Category | What it receives on Fluxer |
|---|---|
| Server | Community channels, roles and settings, emojis, stickers, webhooks, invites, bot configuration changes, permission errors, command actions (!nuke, !toggle-lock, !role-all, !say, !snipe), polls, giveaways, suggestions |
| Messages | Deleted and edited messages, bulk deletions, cleanups made with !clear |
| Members & profiles | Leaves, nicknames, roles, timeouts, bans and unbans, avatars and names, infraction deletions |
| Joins | Joins, joins during raid mode |
| Voice | Connections, disconnections, channel switches, muted mic and sound, camera and screen share, forced disconnections |
| Moderation & sanctions | Warnings, timeouts, kicks, bans, voice disconnections, sanctions from the website, bans from a blacklist alert, reports |
| Anti-raid | Anti-raid actions and settings, honeypot, raid mode |
| Invites | Invite used on join, inviter on leave |
| Captcha | Successful and failed captchas |
Tip
Keep these channels private and reserved to your team: they contain the text of deleted messages and the reasons of sanctions.
What Fluxer doesn't have
Fluxer has no boosts, scheduled events, integrations, AutoMod or stages: the matching logs of the Discord version don't exist on Fluxer.
Critical logs and emergency mentions
Who is warned, and how.
Some logs are critical: everything posted in the Anti-raid and Moderation & sanctions categories, and in Server the channel or role deletions and community changes. The bot adds emergency mentions to them, which really notify the people concerned.
By default, the community owner is mentioned. To choose who to warn, open the dashboard's Basic configuration page, Emergency mentions & alerts section:
| Setting | Effect |
|---|---|
| Security alerts | On (default): mentions are added. Off: no mention. |
| Emergency roles and users | Who is mentioned (the owner if nobody is chosen). |
| Copy by direct message | With Dispatch.IO Basic or Ultimate: the log is also sent by direct message to the emergency users, at most one message every 30 seconds per person. |
Every channel deletion is critical
The bot deletes channels itself: empty temporary voice channels, deleted tickets, !nuke. Each produces a critical log. If you use these modules, pick suitable recipients (a staff role rather than the owner).
Dispatch.IO updates
The Dispatch News & Patches channel (Channels page) is not a log of your community: the Dispatch.IO team posts its patch notes there, sent to every community that picked this channel.
Logs on the website
The dashboard's Configuration logs page keeps the history of changes made on the website, independently of the log channels (see Logs).
When something goes wrong
| What you see | Explanation and fix |
|---|---|
| No log arrives | The log is off or filtered, the channel isn't set, or the bot can't write there (View channel, Send messages, Embed links). |
| The author of an action doesn't show | The bot lacks the View activity log permission. |
| The owner is mentioned all the time | That's the default emergency mention setting: pick other recipients. |
| The invite used isn't identified | The bot lacks Manage community, or several invites were used at the same time. |