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

Automatically expand log line groups #41198

Open
2 tasks done
mjohansenwork opened this issue Aug 1, 2024 · 4 comments
Open
2 tasks done

Automatically expand log line groups #41198

mjohansenwork opened this issue Aug 1, 2024 · 4 comments
Assignees
Labels
area:logging area:UI Related to UI/UX. For Frontend Developers. kind:feature Feature Requests

Comments

@mjohansenwork
Copy link

Description

Is there a way to automatically expand grouping of log lines? When I am debugging a task failure, I often need to look at the Post task execution logs to find out why a task failed. Manually expanding that log group every time I'm debugging is tedious.

Use case/motivation

It would be great to have a feature to either:

  • Automatically expand specific log groups
  • Disable log grouping for specific log groups

It looks like the post execution group start is printed on this line of code.

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@mjohansenwork mjohansenwork added kind:feature Feature Requests needs-triage label for new issues that we didn't triage yet labels Aug 1, 2024
@dosubot dosubot bot added the area:logging label Aug 1, 2024
mjohansenwork added a commit to mjohansenwork/airflow that referenced this issue Aug 1, 2024
This change automatically expands the `Post task execution logs` log group to make debugging easier.

See issue apache#41198
@mjohansenwork
Copy link
Author

#41201

@shahar1 shahar1 added area:UI Related to UI/UX. For Frontend Developers. and removed needs-triage label for new issues that we didn't triage yet labels Aug 2, 2024
@jedcunningham
Copy link
Member

@mjohansenwork doesn't #40146 solve this problem? That's coming in 2.10.

@mjohansenwork
Copy link
Author

I saw #40146, but that only prints the actual exception, right? What about additional debug lines that are printed post-execution, for example as part of the on_failure_callback?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:logging area:UI Related to UI/UX. For Frontend Developers. kind:feature Feature Requests
Projects
None yet
Development

No branches or pull requests

3 participants