cmarteepants opened a new issue, #53050:
URL: https://github.com/apache/airflow/issues/53050

   ### Body
   
   ### View
   DAG View - Audit Log Tab
   
   <img width="1472" height="795" alt="Image" 
src="https://github.com/user-attachments/assets/985635f0-f9fe-486e-a35e-93ac85dfe934";
 />
   
   ### Filters to Add
   
   - Filter by **Event Type**  
     ↪ Focus on specific types of changes (e.g., trigger, patch, retry) for 
easier debugging or auditing
   
   - Filter by **User**  
     ↪ Track changes or triggers made by specific users for accountability and 
investigation
   
   - Filter by **Run ID**  
     ↪ Narrow down audit entries to a specific DAG run when debugging or 
reviewing historical activity
   
   - Filter by **Task ID**  
     ↪ Isolate changes related to a particular task (e.g., task retries, 
clearing actions)
   
   - Filter by **Try Number**  
     ↪ Investigate retries or understand the progression of failed attempts on 
a specific task
   
   - Filter by **Map Index**  
     ↪ Useful when debugging mapped tasks to understand which specific 
iteration had issues
   
   ### API Support  
   
   ⚠️ Partial
   
   - Audit log entries are retrieved per DAG
   - API supports filtering by some fields, but query parameters are not 
consistently exposed in UI or public API
   - Requires extending API to support structured filtering on audit metadata
   
   ### UI Impact  
   
   - Filters could be added above the audit log table
   - Enhances ability to perform root cause analysis on user-initiated changes, 
retries, and failures
   
   ### Notes  
   
   - Current audit log is helpful but difficult to navigate without filtering
   - These filters would improve security auditing, user accountability, and 
debugging workflows
   
   ### Committer
   
   - [x] I acknowledge that I am a maintainer/committer of the Apache Airflow 
project.


-- 
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]

Reply via email to