Reduce Dag processor log noise from per-Dag run lookups#69452
Merged
Conversation
_RunInfo.calculate logged at INFO level on every parse round for every Dag, flooding logs in deployments with hundreds of Dags with messages that carry no operator-actionable signal. Downgrade these to DEBUG.
jason810496
approved these changes
Jul 7, 2026
Member
There was a problem hiding this comment.
LGTM, no harm to suppress the logging (I double check the time when there info were introduced, and they are all introduced 6 months ago in 230293c)
Contributor
|
Hi maintainer, this PR was merged without a milestone set.
|
Contributor
Backport successfully created: v3-3-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Why
_RunInfo.calculateemitted fourINFO-level log lines for every Dag on every parse round.What
_RunInfo.calculate(airflow-core/src/airflow/dag_processing/collection.py) fromlog.infotolog.debug:DEBUG.Was generative AI tooling used to co-author this PR?
If generative AI tooling has been used in the process of authoring this PR, please
change below checkbox to
[X]followed by the name of the tool, uncomment the "Generated-by".Generated-by: [Claude] following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.