Skip to content
Axaro

Logs

Live

What happens on the server, in Discord and in the dashboard.

Three categories

Grouping by category rather than by event is deliberate: nobody wants to tick thirty boxes. Each category can target its own channel, which keeps moderation apart from everyday noise.

CategoryEvents
messagesDeletions, edits with before and after, bulk deletions
membersJoins, leaves, kicks, bans and unbans, roles and nicknames
serverChannel and role creation and deletion

Who did what

Discord does not attach the author to gateway events. Without reading the audit log, a deletion by a moderator would be indistinguishable from a deletion by the message’s author, and every kick would look like a simple leave.

Axaro therefore needs the View Audit Log permission. Without it, the log still works, but without naming who stepped in.

How long it is all kept

The log is kept for 365 days. A daily cleanup deletes anything older: without it, the table would grow forever, an active server writing several thousand lines a day.

Security alerts nobody has handled survive the cleanup: an alert nobody looked at is precisely the one that must not be erased.

Channel and dashboard

Each event goes out twice: to the Discord channel so the team sees it pass by, and to the database so the dashboard can read it back. Writing to the database never blocks sending the message — a late log is better than a missing one.

  • Bots can be ignored, otherwise the log fills itself.
  • Up to fifty channels can be excluded entirely.
  • A message missing from the cache is not logged: the line would be empty.
Discord logs: deleted and edited messages, joins · Axaro