Oliver Kieselbach
469c692866
Event types were defined in 3 hand-maintained, drifted copies: Constants.EventTypes (C#, incomplete — most types were raw string literals at ~70 V2 emit sites), KNOWN_EVENT_TYPES (MCP search), and EVENT_TYPES_CATALOG (MCP resource). The MCP catalog advertised 6 phantom types that are never emitted and omitted ~80 real ones, silently degrading the now event-TYPE-driven cross-session search recall. Make Constants.EventTypes the ONE canonical source: - Add 60 consts (49 V2/both + 11 legacy V1 types kept so historical V1 sessions stay analyzable). Refactor ~70 V2 emit sites from literals to consts (values byte-identical; persisted strings matched by rules/UI/MCP). V1 emit sites left untouched (decommissioning). - Guard test (V2): scan V2 source for the 6 emit shapes, assert every literal is defined in Constants.EventTypes — prevents re-drift. A deeper sweep this test validated also caught 11 emitted types the initial audit missed (local-var emit shape): whiteglove_part1_complete, hello_*, hello_wizard_started, esp_failure, esp_exiting. - MCP: resource-catalog.ts becomes the single TS source (130 types, 21 groups); KNOWN_EVENT_TYPES derives from it; shadow_discrepancy marked internal (searchable, not advertised). Drift test reads Constants.cs and asserts catalog ∪ internal === C# values. Pure refactor — no event-type string value changed. Tests: DecisionCore 357/357, V2.Core 1186/1186 (incl. guard), MCP 109/109, all tsc/build green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Autopilot Monitor
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.
Private Preview
Autopilot Monitor is currently running as a Private Preview. Visit autopilotmonitor.com to request access and learn more.
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 documentation is available at autopilotmonitor.com/docs
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.