Repository navigation
Feature expand health endpoint reporting - #70416
Merged
vincbeck merged 21 commits intoAug 28, 2026
Merged
Conversation
boring-cyborg
Bot
added
area:API
JH-A-Kim
force-pushed
the
feature-expand-health-endpoint-reporting
branch
10 times, most recently
from
July 29, 2026 22:39
1399c6d to
a49a683
Compare
JH-A-Kim
marked this pull request as ready for review
July 30, 2026 02:46
JH-A-Kim
requested review from
bbovenzi,
bugraoz93,
choo121600,
dheerajturaga,
dstandish,
ephraimbuddy,
guan404ming,
henry3260,
hussein-awala,
pierrejeambrun,
potiuk,
rawwar,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
July 30, 2026 02:46
When a triggerer or Dag processor job is created, the team/bundle name field is added into its Job instance. These fields have been added to the Job class as strings and list of strings.
Without these assertions, regressions in how triggerer team_name and Dag processor bundle_names flow into Job rows and the monitor health response could slip through. including degraded multi-instance status and get_jobs_health filtering/ordering.
Operators using HA components need the documented response shape so they can rely on detailed_status and instances instead of assuming a single scheduler/triggerer/Dag processor heartbeat.
Removed state=RUNNING and added end_date=None to query for jobs. This matches the pattern in trigger.py. Removed the logic which returns status=None if the retrieved job list is empty. Updated tests to check for this new logic, and added DB tests that do not mock the job retrieval.
team_name as an arg to the class is redundant since it has been added to Job. Callers for this class will be required to set team_name on Job.
Tegh25
force-pushed
the
feature-expand-health-endpoint-reporting
branch
from
August 27, 2026 21:38
ee97a18 to
1bc2326
Compare
Contributor
Resolved 🙂 |
ferruzzi
approved these changes
Aug 27, 2026
ferruzzi
left a comment
ferruzzi
left a comment
Contributor
There was a problem hiding this comment.
Nice work, thanks to both of you for seeing this through to the end, it's been a long ride.
Contributor
Author
|
Thank you for being an incredible mentor! I'll see you both around the repo and slack (and eventually when I come back from my internship lol) (and also on my other pr that I haven't had time to get back to) |
imrichardwu
pushed a commit
to imrichardwu/airflow
that referenced
this pull request
Sep 11, 2026
1 task
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
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.
Description
These changes act as an implementation for the suggested changes in the design proposal:
Design propsoal
and from the Discussion from the following thread and lazy consensus on the dev list:
DISCUSS
LAZY CONSENSUS
These changes were co authored by @JH-A-Kim and @Tegh25
The changes are the following:
Side Note: There was a slight change from using
unhealthytodownindetailed_statusfor clarity.Was generative AI tooling used to co-author this PR?
Generated-by: [Sonnet 5] 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.