Change 649816 had a related patch set uploaded (by Srishakatux; owner: Srishakatux):
[wikimedia/toolhub@main] [WIP] User interface for audit logs

https://gerrit.wikimedia.org/r/649816

@bd808 As far as the audit logs UI goes, I think what we have in the data looks good. A couple thoughts/ questions:

• Not sure what to do with username null values. Should we filter them on the backend or frontend or show them on the frontend with no name?
• Each log summary could probably be a bit more verbose; it is also that way likely as all message fields are currently empty. For example, I am trying to understand what it means to update a tool or a URL, but not sure.

In T264968#6696794, @srishakatux wrote:

@bd808 As far as the audit logs UI goes, I think what we have in the data looks good. A couple thoughts/ questions:

• Not sure what to do with username null values. Should we filter them on the backend or frontend or show them on the frontend with no name?

I added code to show them as a "System" user on the frontend in PS3.

• Each log summary could probably be a bit more verbose; it is also that way likely as all message fields are currently empty.

All message fields are currently empty largely because the events that are currently tracked are backend actions that we have not exposed a message field to the user for.

For example, I am trying to understand what it means to update a tool or a URL, but not sure.

An update action is recorded when an existing database model is saved. For an URL this is currently not possible through the APIs that have been exposed. For a tool it means that a crawler run has happened and made some sort of change to the tool record, but that may be a "null edit" that really does not alter the record. For a user update actions are currently excluded from audit log recording on the backend.

Change 649816 merged by jenkins-bot:
[wikimedia/toolhub@main] User interface for audit logs

https://gerrit.wikimedia.org/r/649816