What it does
The autoheal crate is a policy engine for health-driven runbooks. A check must fail several consecutive observations before any action fires, actions are cooldown-gated and bounded per incident, and every action is audited before it runs. No part of the server or the command line uses it.
How it works
A check opens an incident after a configured number of consecutive failures and closes it after a configured number of recoveries, which prevents flapping. Each runbook has a cooldown measured in logical ticks and a hard per-incident maximum, and exhausting it disables the runbook until recovery. The cumulative bound is stored in a state file in the data directory, read fail-closed.
Every action is recorded through a fallible audit sink before the actuator moves, and an audit failure withholds the action. Observations carry a logical tick: an absent check resets its counters, and a snapshot whose tick goes backwards is refused. A node serves when no traffic-removal incident is open on any check, and not otherwise. An empty policy heals nothing, and malformed or unreadable bounds disable runbooks and fence serving.
Where you reach it
- Library
kynetra_autoheal policy and incident engine (engine library, not wired to the server)
Limits
- Not reachable from the server or the command line, and no actuator is wired to it.
Evidence
- TestsCovered in the engine repository by about 20 tests for thresholds, cooldowns, audit ordering, freshness and fail-closed behaviour
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
This is not available in the preview. Request a preview to discuss the current scope.