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.

Sign up for GitHub

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

Jump to bottom

Improve debug logging #43186

Open
2 tasks done
rawwar opened this issue Oct 19, 2024 · 3 comments
Open
2 tasks done

Improve debug logging #43186

rawwar opened this issue Oct 19, 2024 · 3 comments
Assignees
@rawwar
Labels
area:logging kind:feature Feature Requests kind:meta High-level information important to the community

Comments

@rawwar
Copy link
Collaborator

rawwar commented Oct 19, 2024 •
edited
Loading

Description

Identify and improve debug logging in core and providers. Debug logs should include all the information used to make the request/invocation, especially when interacting with external systems.

Use case/motivation

It helps identify the data used when interacting with external systems and response data. This can be very helpful in case of failures. Many providers already do this. But, goal of this issue is to identify gaps and fill them

Related issues

Parent Issue: #40975

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct
@rawwar rawwar added kind:feature Feature Requests needs-triage label for new issues that we didn't triage yet labels Oct 19, 2024
@dosubot dosubot bot added the area:logging label Oct 19, 2024
@omkar-foss omkar-foss added kind:meta High-level information important to the community and removed needs-triage label for new issues that we didn't triage yet labels Oct 23, 2024
@Prab-27
Copy link
Contributor

Prab-27 commented Dec 19, 2024 •
edited
Loading

@omkar-foss, I'd like to work on this issue. I would like to start with the scheduler

@rawwar
Copy link
Collaborator Author

rawwar commented Dec 19, 2024 •
edited
Loading

@Prab-27 , feel free to create issues and refer them to this one. We can use this as an Issue to track progress. I'll start tracking them here once you link the issue.

@rawwar rawwar self-assigned this Dec 19, 2024
@omkar-foss
Copy link
Collaborator

omkar-foss commented Dec 20, 2024 •
edited
Loading

Sure thanks for picking it up @Prab-27, feel free to create a new issue for the Scheduler debug logging improvements and link it to this issue (as @rawwar suggested above).

Also in case you'd like to discuss or brainstorm something quickly, you can drop a message on #sig-improving-debugging channel on Airflow community Slack, link here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rawwar rawwar

Labels
area:logging kind:feature Feature Requests kind:meta High-level information important to the community
Projects
Debugging Improvements - Airflow 3
Status: Planning
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rawwar @omkar-foss @Prab-27