davsclaus opened a new pull request, #29504:
URL: https://github.com/apache/camel/pull/29504
_Claude Code on behalf of davsclaus_
The Health tab was a table of checks. Most of them are the ones Camel runs
on its own (the context, the route controller, the security policy, a check per
route and per consumer), and they all said UP, which told little. The tab now
opens on a page with two states.
**All UP:**
```
๐ All good
ready โ live โ 7 checks UP
up since 17:35:47 (20s) ยท checked 40 times ยท never failed
Camel checks on its own: the context, the route controller, the security
policy, 2 routes and 2 consumers
Your checks: none
ready โโโโโโโโโโโโโโโโโโโโโ
live โโโโโโโโโโโโโโโโโโโโโ
```
The checks you wrote yourself are named one by one, even when UP. A check
counts as Camel's own when its group is `camel` and its id is one Camel uses:
`context`, `route-controller`, `security-policy`, `route:*`, `consumer:*`,
`producer:*`.
**Not all UP:** the title says `NOT READY` or `NOT LIVE`. The checks that
are not UP come first, each with:
- since when it has been in that state,
- its message,
- how often it failed, out of how many checks,
- when it was last UP.
Then the page says what that means for the integration: when not ready,
Kubernetes would take it out of the service; when not live, it would restart
it. The other checks fold into one line.
**Under both:** a strip of ready and live, second by second, as the TUI read
them (`HealthHistory`, kept for 5 minutes). A check that went DOWN and came
back between two looks at the tab shows there, with `down 5s, the last at โฆ`.
**Also:**
- `t` shows the checks one by one in the table as before, and `d` there
shows only the DOWN ones.
- The More menu has a `DOWN` badge on Health while a check is DOWN.
- The details of each check (`success.start.time`, `failure.start.time`,
`success.time`, `invocation.count`, `failure.count`, `failure.time`) are now
parsed from the status.
- `tui_get_table` gives `ready`, `live` and, per check, `builtIn`, `since`
and `failures`.
The help page (health.md) describes the page.
**Tests:**
- `HealthTabRenderTest`: all good, a check DOWN, and a flap in the strip.
The existing table tests now open the table with `t`.
- `StatusParserTest#healthDetailsSayWhenAndHowOften`.
- The full `camel-jbang-plugin-tui` suite passes. I also ran it on current
main with all my open TUI PRs merged together (#29493, #29495, #29496, #29500,
#29503): 2452 tests, all green.
- I checked the all-good page live with the `fail-well/circuit-breaker`
example. That example has no check that goes DOWN, so the unit test covers the
DOWN state.
๐ค Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
