Repository navigation
Conversation
This was referenced Oct 28, 2026
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
alex289
force-pushed
the
feat/health-service-status
branch
from
October 28, 2026 13:16
9fd4fbc to
10f946d
Compare
timokoessler
approved these changes
Oct 28, 2026
Agents now include the health of each compose service in their status reports. The hub derives a new degraded status when some services are healthy while others are unhealthy or stopped. Older agents keep working because the aggregate status is unchanged.
alex289
force-pushed
the
feat/health-service-status
branch
from
October 28, 2026 19:45
10f946d to
43ef27a
Compare
This branch has not been deployed
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.
Type of change
Description
Part 1/4 of #268 (health status stats). Agents now report the health of each compose service, and the hub derives a new
degradedapplication status when some services are healthy while others are unhealthy or stopped.Agent
ApplicationStatusgains arepeated ServiceStatus servicesfield. The agent groups containers bycom.docker.compose.serviceand applies the existing aggregation per service.unhealthy.Hub
unhealthy). The hub turnsunhealthyintodegradedwhen at least one service is healthy. Mixed versions keep working: an old agent sends no services and staysunhealthy, and an old hub ignores the new field.degradedcounts as unhealthy for notifications: healthy→degraded sends the unhealthy notification, degraded→healthy the recovery one, and degraded↔unhealthy is silent.Frontend
Degradedbadge. Degraded apps fall into the fleet's "unhealthy" category, with their own attention reason.