Vasu-Madaan opened a new issue, #68334: URL: https://github.com/apache/airflow/issues/68334
### Description Airflow 3 Audit Logs currently expose the raw `owner` value in the UI "User" column, but do not expose `owner_display_name` through the `/api/v2/eventLogs` public API response. For installations where the auth manager stores an internal user ID in `owner`, this makes audit records difficult for end users and compliance teams to interpret. The `log` table already has an `owner_display_name` column, and `airflow.models.log.Log` includes `owner_display_name`, but `EventLogResponse` currently returns only: ```text owner ``` It does not return: ```text owner_display_name ``` The Audit Log UI therefore renders the raw `owner` value for the "User" column. It would be helpful for `/api/v2/eventLogs` to include `owner_display_name`, and for the Audit Log UI to display the display name when present, falling back to `owner` when it is not present. ### Use case/motivation Some organizations use the Audit Log page and `/api/v2/eventLogs` endpoint for compliance workflows, especially to review manual DAG triggers. For manual DAG trigger audit records: - `owner` may be an internal opaque user identifier - `owner_display_name` may contain a human-readable name - the trigger note is currently buried inside the expandable `extra` JSON payload This makes it hard to answer basic audit questions such as: - who manually triggered this DAG run? - what note or incident/change ticket was entered when it was triggered? Suggested improvements: - add `owner_display_name` to `EventLogResponse` - display `owner_display_name || owner` in the Audit Log UI "User" column - optionally expose common manual-trigger fields, such as `extra.note`, more prominently in the UI or as filterable/searchable data ### Related issues I found related audit-log issues, but not this specific display-name/API contract request: - #55074 covers incorrect pause/unpause audit payloads - #59965 covers an incorrect/slow event-log task-instance join ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's Code of Conduct -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
