Improve query audit log including user
- Dominant language
- Java
- Stars
- 6.1k
- Forks
- 1.5k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 195
Description
Pinot currently supports query audit logging. I can check in controller or broker log files.
(example)
```
url string passed is : http://:7001/query/sql
Query: select avg(score) from transcript_sunny group by subject Time: 213
Handled request from POST http://:9001/sql, content-type application/json; charset=UTF-8 status code 200 OK
```
But it will be a good enhancement to log the user in query.
In production, I think it is important point.
cc. @kishoreg
Contributor guide
Research direction
Start by locating the query audit logging paths for the controller and broker, including handling for the /query/sql and /sql endpoints shown in the examples. Determine how the authenticated user is available at those points; done means audit entries include that user alongside the query and existing request details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100