bvandeusenandClaude Opus 5.5 4ded8ecee4 fix(mcp): get_anomaly shows a quick Steward restart, not only a gap over 90 s (#5862) ...

A redeploy's new process ticks at once, so its once-a-minute samples never
broke for 90 s and get_anomaly showed none of the day's restarts. The first
self-monitor tick in a process now records restart_gap_secs (time since the
last process's last sample), and steward_gaps shows each one as a restart.

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

2026-10-15 16:11:27 -04:00

..

alerting.md

fix(mcp): get_anomaly shows a quick Steward restart, not only a gap over 90 s (#5862)

2026-10-15 16:11:27 -04:00

ansible.md

fix(ansible): overlapping runs: one per host, one per schedule, one action run per alert rule (#5158)

2026-10-06 21:24:51 -04:00

backups.md

feat(mcp): Steward's own backups: the runs, the next one, checking and making one (#5836)

2026-10-15 13:09:12 -04:00

configuration.md

chore: rename project Roundtable → Steward

2026-04-25 16:20:14 -04:00

mcp.md

fix(mcp): get_anomaly shows Steward's own restarts beside every anomaly, and a router's containers (#5862)

2026-10-15 15:58:28 -04:00

monitors.md

chore: rename project Roundtable → Steward

2026-04-25 16:20:14 -04:00