Logs should use tags not single types

[Chief-Engineer]

Description

Logs currently use log types. Each log can be one type. To allow better filtering, each log should be able to have multiple tags.

Some log types fit into categories, like hit logs. Having a shared tag for these would be helpful for when admins try to figure out who attacked people. Ahelps don't usually specify, so admins need to either ask or select all 3 log types in the filter. While selecting 3 log types doesn't take a long time, it'd be a minor QOL change and the time savings would add up.

Some log types group a system/item, like RCD, while others group in-game results, like Construction/EntityDelete. Neither is best in all cases and having both will result in some overlap. Tags allow both types to be used in logs, allowing admins to use whichever is best in the situation.

Scenario

A wall is missing into the armory, an admin wants to figure out who took it down. They don't have the entity uid for the wall because the wall doesn't exist anymore and there are too many walls on the station to just search the prototype.

Currently

An admin has to know every log type that may log a deletion/deconstruction in addition to EntityDelete, filter by those and search the wall prototype, then sift through logs that are unrelated to deletions, because types like RCD will log creations of walls too.

Tagged system

An admin can filter to only EntityDelete which would include every log that results in a deletion of an entity, then search the wall prototype. There would still be logs for deletions of other walls, but every log would be a deletion of a wall.

Other Examples

• Hit logs are currently separated into MeleeHit, BulletHit, and HitscanHit. There's also a Damage log type that's used for other things. A melee hit log should be tagged with the following types MeleeHit Hit Damage. Hit could/should be a metatype, since all hit logs would be part of a more specific type, but Damage is currently used for things that don't fit in a more specific category so it can't be a metatype.
• Actions performed by someone who is adminned could have an Admin tag added to whatever they'd normally have. There are better ways to do this, but doing this with something like including the info in the json for the entity could aid in filtering.
• RCD and Delete are their own types. The RCD can delete things, but it is not the only thing that can generate a log while deleting something, and not all RCD logs are for deleting something. Logs for the RCD deleting something should be tagged as both RCD and Delete.
• A tag could be created for power being toggled on a device, which would apply to thing like toggling APCs, the AME, and PA. Tags could be created for each major power source, AME and singularity, which would apply to things like changing their settings, in addition to togging their power. These tags would overlap without any being fully part of another. With updates to log viewers, admins could filter for logs with both the power toggle and AME tags to easily find who toggled the power on the AME without having to know the exact format of the AME power toggle log to search it.

[juliangiebel]

I already fear the massive migration and index building 😰 I definitly agree though

[PJB3005]

The entire storage method for admin logs probably needs to be rethought anyways.