Oliver Kieselbach
1733f4fd48
EffectRunner posts ClassifierVerdictIssued from inside DecisionStepProcessor.ApplyStep, i.e. on the SignalIngress worker thread. With the bounded channel (256) full, Post's back-pressure slow path blocked the channel's only consumer as a producer: nothing could ever drain, every collector Post blocked behind it, and the whole decision/monitoring pipeline froze silently until the max-lifetime watchdog. Post now detects a call from the worker thread itself and routes the item to a worker-local follow-up queue that WorkerLoop drains (iteratively, ahead of the channel) right after the current item. Same processing path — ordinals, SignalLog, emit, reduce, ApplyStep — just never blocking. Worker posts are accepted during the Stop drain too, since the verdict belongs to the step being finished. ReentrantPostCount exposed for observability/tests. Tests: full channel + worker post releases a blocked foreign producer and processes the verdict before the next channel item (fails against the previous code by hanging); follow-up chain drained in order without recursion; verdict posted during Stop drain is not lost. Docs: agent/decision-engine.md, agent/overview.md, log.md. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
AutopilotMonitor
Advanced monitoring and troubleshooting solution for Windows Autopilot deployments. Gain full visibility into every enrollment session with a detailed event timeline, fleet health dashboards, and session reporting. Define custom analysis rules to automatically detect issues and gather rules to collect targeted evidence. Retrieve diagnostics packages on demand, configure agent settings like auto-reboot behavior and automatic timezone adjustment — all managed centrally from the web dashboard.
Availability
Autopilot Monitor is publicly available — the Community plan is free. Sign in with your work account at autopilotmonitor.com; new organizations complete a short activation step after first sign-in.
Overview
Autopilot Monitor provides real-time tracking, intelligent diagnostics, and automated troubleshooting for Windows Autopilot enrollment processes. It consists of:
- Bootstrap Script — PowerShell script deployed via Intune that starts monitoring early in the enrollment process
- Monitoring Agent — Lightweight .NET application that collects telemetry and evidence during enrollment
- Backend API — Azure Functions-based ingestion and processing pipeline
- Web Dashboard — Next.js application for real-time monitoring and fleet analytics
Architecture
For detailed information about the system architecture, components, and data flow, see Architecture Documentation.
Documentation
Full admin documentation is available at docs.autopilotmonitor.com
License
This project uses a split licensing model:
- MIT License — Agent (
src/Agent/) and Shared library (src/Shared/) — unrestricted use on end-user devices - AGPL-3.0 — Backend (
src/Backend/), Web Dashboard (src/Web/), and MCP Server (src/McpServer/) — server-side components remain open source
See LICENSE for full details.