cmarteepants opened a new issue, #53055: URL: https://github.com/apache/airflow/issues/53055
### Body ### View Browse - Audit Log <img width="1451" height="589" alt="Image" src="https://github.com/user-attachments/assets/5dd54b29-bc34-4c6e-884e-4bf980bfd855"; /> ### View Browse – Audit Log ### Filters to Add - Filter by **Timestamp Range** ↪ Investigate events that occurred during a known incident window - Filter by **Event Type** ↪ Focus on a specific type of change, like config updates, triggers, or deletions - Filter by **User** ↪ Identify who initiated a given change or audit action - Filter by **Extra** ↪ Surface entries with specific metadata payloads, like modified fields or context (e.g., asset ID) ↪ Use a key/value text input pair similar to `conf` filters ↪ Allow partial match for both key and value - Filter by **DAG ID** ↪ Narrow logs to a specific workflow - Filter by **Task ID** ↪ Investigate operator-level changes or task retries - Filter by **Run ID** ↪ Debug changes affecting a particular DAG run - Filter by **Map Index** ↪ Examine audit events for specific mapped task slices - Filter by **Try Number** ↪ Surface retries or manual interventions on specific attempts ### API Support ⚠️ Partial - Audit log API includes relevant fields, but many are not exposed via query parameters - Filtering by time, task, and run-level metadata would need backend support or indexing enhancements ### UI Impact - Add filter panel to the top of the audit log screen - Support multiple entries with an “Add Filter” button or + icon - Would significantly improve investigation workflows and compliance monitoring ### Notes - Enables faster triage and auditability, especially in regulated environments ### 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]
