Write critical operations to the audit log
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
Is your feature request related to a problem? Please describe.
For compliance reasons there should be the possibility to log critical operations into a log file.
Describe the solution you'd like
The server provides an admin_audit app which can be used to track events that apps emit and write it into the audit log
We should implement audit logging for the tables app for the following actions as a starting point:
- A table or view is deleted
- A row is deleted
- A tables ownership is transferred
Describe alternatives you've considered
Writing to the regular Nextcloud log is not feasible as those log messages are rarely relevant to regular administrators
Additional context
Setup documentation: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/logging_configuration.html#admin-audit-log
Developer documentation: https://docs.nextcloud.com/server/latest/developer_manual/basics/logging.html#admin-audit-logging
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Nextcloud admin-audit and developer logging documentation, then locate the entry points for deleting tables or views, deleting rows, and transferring table ownership. Done means each of these three operations emits an event that appears in the admin audit log rather than only the regular Nextcloud log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100