bvandeusenandClaude Opus 5.5 98440d8de6 fix(traefik): count each Traefik process only against its own last scrape (#5844) ...

One metrics URL can reach several Traefik processes: a swarm service's
replicas behind the routing mesh or its VIP, a Kubernetes Service's pods,
a keepalived pair after failover, or the same Traefik after a restart.
Each keeps its own counters, so comparing one with another read the second
one's lifetime totals as new traffic: retired routers flashed 100% 502 and
an idle router showed 834 req/s whenever the scrape moved to the other
replica.

Each scrape is now keyed by Traefik's process_start_time_seconds and
compared only with the same process's previous scrape. A process seen for
the first time (or not in the last hour) sets its baseline and counts
nothing. Without a start time every scrape is one process, as before.

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

2026-10-15 14:36:10 -04:00

..

core

feat(mcp): SNMP devices and Prometheus targets: their state, readings and series (#5840)

2026-10-15 13:31:46 -04:00

plugins

fix(traefik): count each Traefik process only against its own last scrape (#5844)

2026-10-15 14:36:10 -04:00

reference

perf(metrics): a latest-value table for "what is it now"; dashboard cells say loading, failed and as-of (#5208)

2026-10-06 23:06:34 -04:00

superpowers

docs: Ansible inventory infrastructure implementation plan

2026-06-05 18:19:17 -04:00

architecture.md

feat(norms): hosts, containers and monitor response times are graded against their own normal (#5742)

2026-10-14 16:17:04 -04:00