[Feature Request] Enhanced admin Logs - show user and path with relevant errors

[SVerkuil]

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
I manage a AIO nextcloud instance used in a small company setting. Sometimes employees make mistakes with sharing files or webdav configuration. These mistakes can result in errors like Access to this resource has been denied because it is in view-only mode in my admin logs. Therefore I know something is configured wrong for some user on some device, but it is really hard to find out who / where.

Feature request: I would like to see from the admin log web interface (1) which user/device triggered this error and (2) which file (path) is associated with the error.

Describe the solution you'd like
For webdav and device/token misconfiguration related errors I would like to see which user triggered the error and which file (path) the error is applicable to.

Describe alternatives you've considered
Probably I can log in to the server and delve deeper in the logs, but that takes a lot of time to do.

Additional context
See screenshot for the kind of errors I am referring to. I would like to see (1) which app the token is invalid for (2) which user triggered the error and (3) which file path (if relevant) so I can help them fix these issues.

Please note this Nextcloud instance is used in a company setting and does not host peoples private files. Providing more details in logs so we can help employees set up their configuration right should not pose any additional privacy issues as all files and devices are company property.

[susnux]

Thank you for your report!
With Nextcloud 28 you can see that information in the log details modal.

The feature request about seeing it directly in the table, is a duplicate of #24