Enhancement: Separate audit log for privileged requests
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 700
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 11
Description
Is your feature request related to a problem? Please describe.
Currently we have a log of HTTP requests that is maintained for some amount of time. I'm proposing that we implement a separate log that's maintained for much longer (year+?) but that only logs privileged requests, such as requests by admins/staff.
Describe the solution you'd like
Separate log of privileged requests that is maintained for longer periods.
Basic Example
N/A
Describe alternatives you've considered
N/A
Drawbacks and Impact
No response
Additional context
No response
Contributor guide
No contributing guide indexed for this repository
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 by locating the existing HTTP request log and the code that identifies admin or staff requests. Clarify the required retention period, storage, access controls, and exact definition of a privileged request before implementation; done means those requests are recorded separately and retained longer than the current log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100