Replies: 5 comments
-
In the menu Browse -> logs, you may find what you need |
Beta Was this translation helpful? Give feedback.
-
Related to #18217 - maybe you want to cooperate with @alex-astronomer and also add this one @tooptoop4 ? |
Beta Was this translation helpful? Give feedback.
-
Is this not already in place? I know that we have audit logs for task clears, mark success, failure etc. Off the cuff I'd be surprised if this didn't already exist, however I could be wrong. |
Beta Was this translation helpful? Give feedback.
-
It would be helpful to add the triggered_by_user in the DagRun model itself, not just in Audit Log. |
Beta Was this translation helpful? Give feedback.
-
Currently, Audit Log contains event type "trigger" but is it possible to tie a particular trigger event to a dag_run? Is it possible to tie current running task's dag_run to its trigger event log so that I can get the user who triggered it? Lets say, the dag allows multiple active dag runs. A dag can be triggered at the same time by two different user with different config so it is important to tie those two correctly. I was comparing the Audit Log's datetime and dag_run's logical_date and found those two to match in 1 test. Can I assume they will always match to the same precision? |
Beta Was this translation helpful? Give feedback.
-
Description
For audit purposes the username who triggered a dagrun should be logged (or stored in the metadb, shown in UI). Whether they logged into the UI and clicked trigger or used API to trigger a dagrun this should be captured.
ie userX triggered dagrunY with execDateZ
userA triggered dagrunB with execDateC
Use case/motivation
Want to know who interacted with adhoc dagruns
Related issues
no
Are you willing to submit a PR?
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions