mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-08-25 08:52:06 +00:00
f38e95eb72
An enabled Patrol that can never run and one that runs and finds nothing were indistinguishable in the fleet: both presented as high run counts with zero AI calls and zero findings. The install that motivated this sat blocked for over a month because provider initialisation failed once at boot and was never retried; the self-heal landed separately, but telemetry still cannot see which blocked cause dominates in the field. Schema v10 exports the fixed machine cause code (for example provider_not_configured) only while Patrol is in the blocked runtime state. The cause rides the router-owned Pulse Intelligence snapshot into the outbound ping. Blocked-reason text, provider endpoints, model names, and configuration stay on the install; an untyped blocked reason exports nothing rather than free text, and a disabled, active, or mid-run Patrol exports an empty value even when a stale cause is still recorded. |
||
|---|---|---|
| .. | ||
| agents | ||
| aicontracts | ||
| audit | ||
| auth | ||
| cloudauth | ||
| db | ||
| discovery | ||
| diskinventory | ||
| edition | ||
| extensions | ||
| fsfilters | ||
| licensing | ||
| metrics | ||
| pbs | ||
| pmg | ||
| proxmox | ||
| pulsecli | ||
| reporting | ||
| securityutil | ||
| server | ||
| tlsutil | ||