bvandeusenandClaude Opus 5.5 7ce61a2099 fix(traefik): grade routers on their last 15 minutes; the Config tile reads Traefik's reload time (#5355) ...

The operator: problem cards "can disappear so quickly". Each router was
graded on its latest scrape, so a 4xx share near the 1% cutoff crossed it
on one scrape and fell back on the next. recent_window reads every
router's last 15 minutes in one query, the error shares weighted by
traffic; grade_routers uses it on the page and the dashboard widget, and
the why says "over the last 15 min".

traefik_config_last_reload_success is the Unix time of the last good
reload, not a 0/1 flag, so the tile said "Reload failed" on every scrape.
traefik_005 stores it as config_last_reload_at, and the tile reads
"Config reloaded 3m ago". The router index also carries the 4xx share.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-08 08:26:10 -04:00

..

__init__.py

feat(plugins): fold first-party plugins in-tree; bundled + external roots

2026-06-01 08:37:24 -04:00

traefik_001_initial.py

feat(plugins): fold first-party plugins in-tree; bundled + external roots

2026-06-01 08:37:24 -04:00

traefik_002_stats.py

feat(plugins): fold first-party plugins in-tree; bundled + external roots

2026-06-01 08:37:24 -04:00

traefik_003_access_log.py

feat(plugins): fold first-party plugins in-tree; bundled + external roots

2026-06-01 08:37:24 -04:00

traefik_004_covering_indexes.py

fix(traefik): the rows page reads every router's history in one index-only query (#5355)

2026-10-08 08:20:09 -04:00

traefik_005_reload_at.py

fix(traefik): grade routers on their last 15 minutes; the Config tile reads Traefik's reload time (#5355)

2026-10-08 08:26:10 -04:00