To set up logs with the Dyno bot in Discord, make a private text channel that Dyno can see and post in. Then open the Dyno dashboard, turn on the Action Log module, choose that channel, and tick the events you want, such as message edits and deletes. If edit or delete logs never appear, it is almost always one of four things: a channel permission override blocking Dyno, the event not being ticked, the channel or member being on an ignore list, or the message being older than what Dyno has stored.
Checked on each bot's own site or docs on 3 November 2026. We make PeakBot. Nobody paid to be in this post.
This guide is about Dyno, the Discord bot at dyno.gg, not Heroku "dynos". It covers the Discord side first, then Dyno, then a list of fixes, then how PeakBot does the same job.
Dyno logs vs Discord's Audit Log
These are two different things, and a lot of tutorials mix them up.
- Discord's Audit Log is built into every server. On desktop, right-click the server name, choose Server Settings, then Audit Log. You need the View Audit Log permission. It records moderator actions like bans, kicks, role changes and channel edits, and keeps entries for 45 days. When a moderator deletes someone else's message, it records that a message was deleted, with a channel and a count. It never shows the message text, and Discord does not offer it as a channel feed.
- A bot log (Dyno's Action Log) is the bot posting events into a channel you choose, as they happen. The bot saw the message arrive, so it can show what the message said before it was edited or deleted.
If you want to know what was deleted, you need a bot log. If you want to know who removed it, the Audit Log is still where you look.
Step 1: Make a private log channel in Discord
Do this before you touch Dyno. Most "logs not showing" problems start here.
Desktop
- Create a text channel, for example
#dyno-logs. Put it in a staff category if you have one. - Hover over the channel name and click the gear icon to edit the channel. You need the Manage Channels permission.
- Open the channel's permissions section.
- For @everyone, deny View Channel. This hides the channel from regular members.
- Add your moderator role and allow View Channel.
- Add Dyno's role (or the Dyno bot itself as a member) and allow View Channel, Send Messages and Embed Links. If Dyno's own docs ask for another permission for logging, allow that here too.
- Save.
Mobile
- Open the channel and tap the channel name at the top of the screen.
- Tap Settings, then open the permissions section.
- Make the same changes as steps 4 to 6 above.
Discord's permissions guide shows where these menus are.
Why step 6 matters. Discord applies permissions in layers: @everyone's server permissions first, then the member's role permissions, then channel overrides for @everyone, then channel overrides for roles, then overrides for that one member. Within each layer, denies are applied before allows. Discord's developer docs on permissions set out this order. In practice, if you deny @everyone in step 4 and forget to add Dyno, Dyno's server role does not rescue it, and the bot cannot see the channel.
Step 2: Turn on Dyno's Action Log
- Go to dyno.gg, sign in with Discord, and pick your server from the dashboard.
- Find the Action Log module in the module list and turn it on.
- Open its settings and choose
#dyno-logsas the log channel.
Dyno changes its dashboard layout from time to time, and older YouTube videos show older menus. If a name here does not match what you see, Dyno's docs (linked from dyno.gg) have the current one.
Step 3: Pick which events to log
In the Action Log settings, tick the events you care about. For a message log, the two that matter are message edits and message deletes. Most servers also want member joins and leaves, and role and nickname changes.
A practical setup:
- Message edits and deletes go to
#message-logs, because this channel gets busy. - Joins, leaves, bans and role changes go to
#dyno-logs.
If you split events across channels, repeat Step 1 for each one. Every log channel needs its own override for Dyno.
Then look at the ignore settings. You can exclude channels (like a bot-spam channel) and roles (like other bots) from logging. Keep this list short, because anything on it never shows up in your logs.
Why Dyno edit and delete logs don't show up
Work down this list in order. It covers nearly every case.
- Dyno cannot post in the channel. Open the log channel's permissions and check Dyno's role or member entry. It needs View Channel, Send Messages and Embed Links set to allow, with no deny on any role Dyno has. A quick test: if Dyno cannot post a reply in that channel when you run one of its commands, it cannot post logs there either.
- The event is not ticked. Turning on the module does not turn on every event. Open the module and confirm edits and deletes are selected.
- The wrong channel is selected. This is easy to miss if you renamed channels or split events. Check where each event points.
- The channel or member is ignored. If the message was in an ignored channel, or its author has an ignored role, nothing is logged. After permissions, this is the most common surprise.
- The message is older than what Dyno has stored. A bot can only show the text of a message it saw and still has stored. Messages sent before Dyno joined, or older ones it no longer holds, often log with no content or don't log at all. Dyno's docs mention this cache limit. No setting fixes it.
- The deletion was a bulk purge. A mass delete may show up as one bulk entry, not one log per message, depending on how the bot handles it.
- Dyno itself is having trouble. If everything above checks out and logs still stop, check Dyno's status and support channels from dyno.gg.
Finding out who deleted a message
A bot log tells you what was deleted and who wrote it. It usually cannot tell you who pressed delete, because the delete event Discord sends to bots does not say.
To find out, open Server Settings > Audit Log and filter by message deletes around that time. If there is an entry, a moderator or a bot removed the message, and the entry names them. If there is no entry, the author most likely deleted it themselves, because the Audit Log only records deletions of other people's messages. Several quick deletions by the same person may be merged into one entry with a count.
There is more on reading the Audit Log in See who banned, kicked or timed out someone. For a full staff log channel that records warns, mutes and bans, see How to set up a mod log channel in Discord.
How PeakBot does logging
PeakBot's Logging covers message edits and deletes, joins and leaves, voice activity, and every manual mod action, so moderation your staff do by hand ends up in the log too.
- Make the private channel exactly as in Step 1, but give the PeakBot role the overrides instead of Dyno.
- Sign in at peakbot.pro and pick your server. The getting started guide walks through adding the bot.
- Open the Auto Moderation page in the dashboard sidebar. Logging is set up there, not on a page of its own.
- Choose your log channel and save.
Message, join and leave, and mod action logs come with the Free plan. Voice activity logs need a paid plan. Starter is $5.75/month per server, or $48/year. The Moderation wiki page covers the rest of the moderation setup.
PeakBot's logs have the same limit as any bot: they cannot show messages sent before the bot joined your server.
Dyno vs PeakBot logging
| Dyno | PeakBot | |
|---|---|---|
| Where you set it | Action Log module on the Dyno dashboard | Auto Moderation page on the PeakBot dashboard |
| Message edits and deletes | Yes | Yes, Free |
| Joins and leaves | See Dyno's docs | Yes, Free |
| Voice activity | See Dyno's docs | Yes, paid plan |
| Manual mod actions | See Dyno's docs | Yes, Free |
| Price | See dyno.gg/upgrade | Free, voice logs from $5.75/month |
Stay with Dyno if it already runs your moderation and the logs above work for you. Having logs in the same bot as your mod commands is simpler, and logging alone is not a reason to switch. Pick PeakBot if you want manual mod actions logged alongside message logs, or voice activity in the same place. If you do switch, How to migrate from Dyno to another Discord bot explains how to move without losing your setup.
Frequently Asked Questions
Why isn't Dyno logging deleted messages?
Check these in order. Dyno needs View Channel, Send Messages and Embed Links on the log channel. The delete event has to be ticked. The channel and the author can't be on an ignore list. The message has to have been sent after Dyno joined. The most common cause is a channel override that denies Dyno.
Why doesn't Dyno show who deleted a message?
Discord's delete event does not tell bots who deleted a message. Check Server Settings > Audit Log instead. If a moderator removed it, an entry will name them. If there is no entry, the author probably deleted it.
Can I see messages deleted before I added Dyno?
No. A bot cannot show text it never saw. Discord's Audit Log may show that a moderator deleted a message in the last 45 days, but never what the message said.
How do I log different events to different channels in Dyno?
In the Action Log settings, point each event at its own channel, for example edits and deletes to #message-logs and joins and bans to #dyno-logs. Each channel needs its own permission override for Dyno.
What's the difference between Discord's Audit Log and Dyno logs?
The Audit Log is built into Discord. It lives in Server Settings, keeps entries for 45 days and shows who did what, but never message text. Dyno's logs are posted to a channel by the bot and can show what edited and deleted messages said.
Does PeakBot log voice activity for free?
No. Voice activity logs need a paid plan. Message edits and deletes, joins and leaves, and manual mod actions are logged on the Free plan.
