Uh oh!
There was an error while loading. Please reload this page.
Show the task ID attributes (ti_id, task_id, etc.) once, not on every log line - #66036
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
… log line A recent PR changed the structured log output to include these attributes on every log message, which is very helpful for when the task logs make it to an external system, but when viewing them in Airflow directly it quickly becomes "noise" as they never change. This PR "extracts" them out and shows them once at the the start just after the source info and removes it from every other message. They are also injected back in to the copy and download content
d7d868a to
169b055Compare
bbovenzi
left a comment
There was a problem hiding this comment.
Yeah this is good. Later on we need to clean up our frontend log processing code.
Uh oh!
There was an error while loading. Please reload this page.
Backport failed to create: v3-2-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker d139d37 v3-2-testThis should apply the commit to the v3-2-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
… log line (apache#66036) A recent PR changed the structured log output to include these attributes on every log message, which is very helpful for when the task logs make it to an external system, but when viewing them in Airflow directly it quickly becomes "noise" as they never change. This PR "extracts" them out and shows them once at the the start just after the source info and removes it from every other message. They are also injected back in to the copy and download content
… log line (#66036) A recent PR changed the structured log output to include these attributes on every log message, which is very helpful for when the task logs make it to an external system, but when viewing them in Airflow directly it quickly becomes "noise" as they never change. This PR "extracts" them out and shows them once at the the start just after the source info and removes it from every other message. They are also injected back in to the copy and download content (cherry picked from commit d139d37)
… log line (#66036) (#66421) A recent PR changed the structured log output to include these attributes on every log message, which is very helpful for when the task logs make it to an external system, but when viewing them in Airflow directly it quickly becomes "noise" as they never change. This PR "extracts" them out and shows them once at the the start just after the source info and removes it from every other message. They are also injected back in to the copy and download content (cherry picked from commit d139d37)
… log line (#66036) (#66421) A recent PR changed the structured log output to include these attributes on every log message, which is very helpful for when the task logs make it to an external system, but when viewing them in Airflow directly it quickly becomes "noise" as they never change. This PR "extracts" them out and shows them once at the the start just after the source info and removes it from every other message. They are also injected back in to the copy and download content (cherry picked from commit d139d37)
A recent PR (#65458) changed the structured log output to include these attributes on every log message, which is very helpful for when the task logs make it to an external system, but when viewing them in Airflow directly it quickly becomes "noise" as they never change.
This PR "extracts" them out and shows them once at the the start just after the source info and removes it from every other message.
They are also injected back in to the copy and download content
Before:

After:
(It's much more noticeable on longer logs)