Logging system

[Armaldio]

We need improved logging system to better keep track of incidents without relying on users

Proposal

• Rotating log (everything older than 1 week (?) is deleted)
• Stored as JSON on the server
• With media support (Copy every link on a hidden channel to keep living reference to the file)
• Can be queried from an external interface

Logged events

• channelCreate
• channelDelete
• channelUpdate
• debug
• emojiCreate
• emojiDelete
• emojiUpdate
• error
• guildBanAdd
• guildBanRemove
• guildCreate
• guildDelete
• guildIntegrationsUpdate
• guildMemberAdd
• guildMemberRemove
• guildMembersChunk
• guildMemberSpeaking
• guildMemberUpdate
• guildUnavailable
• guildUpdate
• invalidated
• inviteCreate
• inviteDelete
• message
• messageDelete
• messageDeleteBulk
• messageReactionAdd
• messageReactionRemove
• messageReactionRemoveAll
• messageReactionRemoveEmoji
• messageUpdate
• presenceUpdate
• rateLimit
• ready
• roleCreate
• roleDelete
• roleUpdate
• shardDisconnect
• shardError
• shardReady
• shardReconnecting
• shardResume
• typingStart
• userUpdate
• voiceStateUpdate
• warn
• webhookUpdate

[Armaldio]

@skymen @TheRealDannyyy How do we handle the "consent" part, if any ?

[TheRealDannyyy]

It's already mentioned in the rules.

[Armaldio]

So, I've added a list of all available events and ticked the one that should be logged in our system.
Do you agree ?

[TheRealDannyyy]

So, I've added a list of all available events and ticked the one that should be logged in our system.
Do you agree ?

Nothing much to say about the events. I'd recommend adding filters later down the line and making it modular, so that further events can be added/removed later.

With media support (Copy every link on a hidden channel to keep living reference to the file)

A link alone won't cut it. Media links only work if the media linked is still online.
We discussed this a while back with Skymen. I have no clue how to workaround this limitation.