Oliver Kieselbach b7f74dbd35 v2 single-rail 5.9a: ImeLogTrackerAdapter add InformationalEvent posts (B29 part 1)
Plan §5.9 / PR #9 — V1 Parity Issue #3: the IME log tracker callbacks now
dual-emit a specific DecisionSignalKind + an InformationalEvent so the Events
table regains the V1-compatible wire shape (esp_phase_changed,
ime_user_session_completed, app_install_started, app_install_completed,
app_install_failed, app_download_started, download_progress) while remaining
on the single-rail signal pipeline.

Changes:
- ImeLogTrackerAdapter: construct an InformationalEventPost from the existing
  ingress/clock; after every EspPhaseChanged / UserSessionCompleted /
  AppStateChanged post, also emit a matching InformationalEvent. EspPhase
  declarations carry the mapped EnrollmentPhase (DeviceSetup / AccountSetup /
  FinalizingSetup) per feedback_phase_strategy.
- AppState handler expanded from terminal-only to all state transitions with
  V1-compatible eventType mapping: Downloading transitions → app_download_started
  + byte updates → download_progress (Debug); Installing/InProgress →
  app_install_started; Installed/Skipped/Postponed → app_install_completed;
  Error → app_install_failed. Payload carries appId/appName/state/intent/
  targeted/runAs/progressPercent/bytesDownloaded/bytesTotal/isError/isCompleted
  + appVersion/appType/detectionResult/attempt, plus error* fields on Error.
- Shared.Constants.EventTypes: add EspPhaseChanged, ImeAgentVersion,
  ImeUserSessionCompleted, DoTelemetry, AllAppsCompleted.
- Adapter tests: refactor to filter the posted-signal list by kind + eventType
  so the dual-emission contract is verifiable. 14 new tests cover the full
  state-transition matrix + payload shape + error-field population; total
  adapter test count 37 (up from 17).

Verification: dotnet build AutopilotMonitor.sln clean; V2.Core test suite
green (552 / 552, up from 538).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-23 15:45:29 +02:00
2026-04-22 19:36:19 +02:00
2026-04-22 19:36:19 +02:00
2026-03-17 18:24:01 +01:00
2026-03-26 07:02:33 +01:00
2026-04-04 19:17:01 +02:00

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.

S
Description
Windows Autopilot & Intune enrollment monitoring: live session timelines, fleet health, diagnostics, and an MCP server for AI-assisted troubleshooting.
Readme AGPL-3.0 60 MiB
Languages
C# 72.7%
TypeScript 25.7%
PowerShell 1%
JavaScript 0.5%