Bernard OmniLogs¶

Overview¶

OmniLogs is Bernard's server-wide event record. It captures the important things happening in your server - members joining and leaving, messages being edited and deleted, voice activity, moderation actions, and much more - and organizes them into a clear, searchable log for your moderation team.

This visibility is what makes subtle abuse easy to catch. A user who quickly deletes a ping, edits a message to hide what they said, or slips in and out of voice channels leaves a trail in OmniLogs even after the original evidence is gone.

OmniLogs and Rapsheets are complementary views of the same underlying activity:

OmniLogs is the chronological, server-wide view. It answers "what happened in my server, and when?"
A Rapsheet is the per-user view. It answers "what has this specific user done?"

How OmniLogs Organizes Events¶

OmniLogs posts events into a single forum channel, using one persistent thread per event category. Instead of scattering logs across many separate channels, your moderation team gets a tidy forum where each category (Moderation, Member, Message, Voice, and so on) has its own thread. This is how OmniLogs works by default for every server.

Setting Up OmniLogs¶

The quickest way to get started is the /omnilogs setup-forum command, which designates a forum channel for OmniLogs and pre-creates a thread for every event category in one step. Once it is configured, Bernard begins logging events to the appropriate threads automatically. You can review the current configuration at any time with the /omnilogs status command.

Note

Setting a forum channel with /omnilogs forum designates the channel but does not create the category threads. Use /omnilogs setup-forum to designate the channel and pre-create all threads in one step.

Event Categories and Types¶

OmniLogs groups every event it tracks into nine categories, and each category gets its own thread in the forum. The table below lists each category and the events it captures.

Category	Events Captured
🎯 Moderation	Bans, unbans, kicks, voice mutes and unmutes, warnings, and timeouts
👤 Member	Members joining the server, leaving the server, and editing their profile (such as a nickname change)
💬 Message	Deleted messages and edited messages
🔊 Voice	Members joining and leaving voice, self-muting and self-deafening, and being server-muted or server-deafened
🤖 AutoMod	AutoMod filter violations
🔔 Notifications	General Bernard notifications
🎭 Reaction	Reactions added to and removed from messages
📁 Channel	Channels created, updated, and deleted
🧵 Thread	Threads created, updated, removed, and deleted

Each category maps to a single thread, so all of that category's events land together in one place.

Separating Message Events¶

Message activity tends to be the highest-volume category in a busy server. You can keep deleted messages and edited messages in separate threads, rather than a single combined "Message" thread, by enabling the /omnilogs separate-messages command.

When enabled, deleted messages go to a "Deleted Messages" thread and edited messages go to an "Edited Messages" thread. When disabled (the default), both share the combined "Message" thread.

Moderation and AutoMod Events¶

OmniLogs is where Bernard's other features surface their activity. Every action from a punishment command emits a corresponding Moderation event (a ban emits a ban event, a kick emits a kick event, and so on), and every AutoMod filter violation emits an AutoMod event. These categories give your team a live feed of moderation activity as it happens, complementing the per-user history stored on each Rapsheet.

Custom Join and Leave Messages¶

Beyond logging member join and leave events, OmniLogs lets you customize the message Bernard posts when a member joins or leaves. Configure these through the omnilogs event user-join and omnilogs event user-leave commands.