howardyoo opened a new issue, #41863: URL: https://github.com/apache/airflow/issues/41863
### Description Currently, the Dag file process manger will produce span that will tell you which DAG file has import error (import error count), but does not currently contain any details of why the import error happened (e.g. stack trace). When the file processor processes DAG file, it produces stack trace and store into database, which can later be accessed. It would be a great feature to: - when dag process manager processes dag file, it will check for errors - when the error is detected, it will access the database to attach the stacktrace as part of the span, as span event. ### Use case/motivation When the dag file process manager encounters import error, it will produce span event containing the relative stack trace so that user does not have to navigate into Airflow UI to see the import error separately. ### Related issues _No response_ ### Are you willing to submit a PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
