Set job labels for traceability in BigQuery jobs #37736
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eladkal
reviewed
Feb 27, 2024
amoghrajesh
reviewed
Feb 27, 2024
uranusjr
reviewed
Mar 5, 2024
uranusjr
reviewed
Mar 5, 2024
uranusjr
reviewed
Mar 6, 2024
uranusjr
approved these changes
Mar 12, 2024
eladkal
approved these changes
Mar 14, 2024
Contributor
Author
|
Looks like there was maybe a timeout in one of the build steps. Is there anything I need to do? |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds the airflow dag ID and task ID as labels to BigQuery jobs. This helps trace the jobs back to their corresponding DAG from audit logs and job history. I personally use this to track BigQuery costs at a DAG/task granularity over time.
Let me know if there is a better place to put this than the
_submit_jobcall.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.