Event logs: post events to Discord channels

With event logs, yurna posts selected events as messages to a channel of your choice. Your team sees right in Discord when, for example, a message is deleted, someone joins or a role is changed. You can set a separate channel for every event.

Event logs complement the server log: the server log is always on and shows everything in the dashboard, while event logs additionally send selected events to Discord.

How to set it up#

1. Create one or more log channels only your team can see, and allow yurna to view and send messages there.
2. Open Dashboard → Moderation → Event logs (/dashboard/<server>/logs). The page itself is titled “Logs” and is also reachable via the Event logs tab in the server log.
3. For each event you want, turn on Enabled and choose the Channel. An event can’t be enabled without a channel.
4. Save. As long as there are unsaved changes, the page reminds you.

Each category shows how many events are active (“3 of 8 active”).

Categories#

• Invites – invite created or deleted
• Messages – sent, deleted, edited, bulk deleted, poll votes
• Threads – created, deleted, updated, thread members
• Server & members – joins, leaves, bans, member and server changes, roles, emojis, stickers, scheduled events, integrations
• Channels – created, deleted, updated, pinned messages
• AutoMod – “AutoMod took action” and AutoMod rules created, updated or deleted
• yurna dashboard – changes made via the dashboard, e.g. commands turned on or off, embed color, public dashboard, vanity URL, giveaways, welcome and goodbye messages, reputation, warnings

Change log#

Who changed what in the dashboard is shown in the Change log under Dashboard → Insights → Change log (/dashboard/<server>/dashboard-logs) – with time, person and, where stored, before/after. More under Change log.

Commands#

yurna also needs the “Manage Server” permission for /logs.

Common problems#

• Nothing arrives in the channel: check that the event is enabled and saved, and that yurna can view and write in the channel.
• Too many messages: events like “Message sent” produce a lot of entries on active servers. Only enable what your team actually reads – everything else is in the server log anyway.

See also#

• Server log
• Automod
• Change log