Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Airflow stack traces configurable and easy-to-understand #43177

Open
1 of 2 tasks
omkar-foss opened this issue Oct 18, 2024 · 0 comments
Open
1 of 2 tasks

Make Airflow stack traces configurable and easy-to-understand #43177

omkar-foss opened this issue Oct 18, 2024 · 0 comments
Labels
area:core kind:feature Feature Requests needs-triage label for new issues that we didn't triage yet

Comments

@omkar-foss
Copy link
Collaborator

Description

As per users' feedback in the Airflow Debugging Survey 2024, 55.2% respondents find stack traces challenging.

Use case/motivation

Goal for this issue:

  • Configure depth of stack trace using a config property like AIRFLOW_STACK_TRACK_DEPTH which can then only show stack trace for that much depth e.g. if AIRFLOW_STACK_TRACK_DEPTH=3 then we show only 3 levels deep stack trace as the stack unwinds.
  • Either depth as above or can use number of lines as well (this will be more of an absolute config as in some case 1 level deep trace can take up all the lines!).
  • Use color coding wherever necessary, and simpler language for the user to understand the stack trace - probably by eliminating any redundant parts of the stack trace wherever possible.

Related issues

Parent Issue: #40975

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@omkar-foss omkar-foss added kind:feature Feature Requests needs-triage label for new issues that we didn't triage yet labels Oct 18, 2024
@dosubot dosubot bot added the area:core label Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:core kind:feature Feature Requests needs-triage label for new issues that we didn't triage yet
Projects
Status: Meta & Planning
Development

No branches or pull requests

1 participant