stroblme 79c74116d1 Health summary: a node is failing after two failures in a row; one is a warning, a good run ends both ...

The summary read degraded for 15 minutes after any single node_error, even
once the node had run well again and including one bad input from a visitor.
The controller now counts a node's failures since it last ran well and notes
when it recovered; both carry across rebuilds and an acknowledgement resets
the count. Two in a row inside the 15 minute window is "failing" (a problem),
one is listed under warnings, and nodes.failing keeps meaning "failing now".

Claude-Session: https://claude.ai/code/session_01SSi5AvZ7pFmySK8zy3NPMh

2026-10-28 12:42:35 +01:00

..

assets

Publish the documentation site: docs.fluksio.com

2026-08-22 05:55:34 +02:00

code

Alerts: configuration, test and search entries are a superuser's; subscribing a browser stays open

2026-10-28 12:40:44 +01:00

concepts

Capability report: PUT /devices/{id}/report, a Capabilities section, offline devices degraded

2026-10-16 17:37:49 +02:00

getting-started

SDK: artifacts work outside a node, run --follow prints status and queue waits, fluksio cancel

2026-10-28 08:07:35 +01:00

interface

Health summary: a node is failing after two failures in a row; one is a warning, a good run ends both

2026-10-28 12:42:35 +01:00

reference

Request log: a hook's secret is masked in uvicorn's lines and the tunnel connector's failure line

2026-10-28 08:41:52 +01:00

stylesheets

Make documentation standalone and generalize examples

2026-10-25 14:43:20 +01:00

index.md

Docs: x86 and arm64, Raspberry Pi included; one container in the start pages

2026-10-16 14:56:08 +02:00

llms.txt

A node's worker label is worker, so a device is only a paired one

2026-10-16 16:56:05 +02:00