PACKET
Sign in

Server logging

a record of what happens

Browse the guide

Keep a record of your server's activity. Packet mirrors joins and leaves, nickname and role changes, bans and kicks, channel and server edits, members using Packet's own features, and Packet's own automated changes, to a log channel in Discord AND a dashboard activity feed on the server's Status page. Route different kinds to different channels, exempt certain roles or channels, choose who each log entry posts as, and set how long the dashboard feed keeps history.

Four events are off until you turn them on, each marked that way under its own kind in Configure: deleted messages (Packet logs that a message was deleted, never what it said), and voice joins, leaves and moves.

A worked example. Send joins and leaves to #member-log, moderation actions (warns, mutes, bans) to a staff-only #mod-log, and everything else to a general #server-log, so staff aren't hunting through one long channel for the entry that matters. Exempt a private staff channel, and changes to it and activity in it stay out of the log. Exempt a role, and entries about members holding it stay out: their joins, leaves, nickname and role changes, bans, kicks, timeouts, voice activity and deleted messages. Packet's own moderation and raid protection entries are always logged. Packet also groups a member's rapid clicks on a role menu into one tidy entry instead of five.

One event at a time. Under each event in Configure → Logging there is a Post to box. Pick a channel there and just that event goes to it, for example voice moves to #voice-log while the rest of the member events stay in #member-log. Leave it empty and the event posts to its kind's channel, or the default one. An event you have turned off posts nowhere, even with a channel picked.

The log channel and the dashboard feed aren't the same record. The channel keeps every message until you delete it yourself; the dashboard feed only keeps what you set it to, up to a year, which is what search and filtering on the Status page run against.

(Configure → Logging.)

Problem reports. When something you set up stops working, Packet tells you instead of failing quietly. A scheduled message, birthday message, social alert or game server board whose channel was deleted or no longer lets Packet post, and a level reward or shop role that sits above Packet's own role, each get one plain message saying what broke, where, and the one fix. It goes to your log channel when logging is on and Packet can post there. If there is none, Packet DMs the server owner instead. You hear about each problem once a day, never more. To stop the DMs, untick DM the server owner when something breaks and there is no log channel in Configure → Logging. That works even while logging itself is off, and reports to your log channel are not affected.

← Back to the guide