Logging
A record of what happened in the server.
Routing
Pick a default channel, then switch on the events you want. Any event can go to its own channel instead, message logs and join logs usually want separating, since one is noise you skim and the other is something you go looking for.
Ignore lists
Exclude channels, whole categories, particular members, or anything a bot did. Bots are ignored by default: a server with three bots posting embeds produces a log nobody reads, which looks like coverage without being it.
Message content
Off by default, Bonki does not read message content. Deletions and edits are still logged: who, where and when. The log says the text is unavailable rather than showing a blank, so you can tell the difference between nothing being said and nothing being kept.
You can switch message logging on, under the toggle at the bottom of this module. Deletions then show what was actually removed, and edits show both versions. Bonki keeps that text for 7 days by default, 30 at most, and deletes it automatically. It never stores anything from your ignore lists, anything a bot posted, or the files behind an attachment, only their names.
This needs a privileged Discord permission, which is a serious thing for a bot to hold. Tell your members before you turn it on. In most places that duty is yours as the administrator rather than ours.
Who did it
Discord does not say who deleted a message or kicked a member in the event itself, only its audit log does, briefly. Bonki checks it, so give it View Audit Log or those entries will show what happened without who did it. A leave and a kick look identical without it.