Oliver Kieselbach
aaacc6ecb2
Sequence is a persisted, strictly monotonic per-session counter assigned at emit time (EventSequenceCounter: locked, saved before return, survives restarts). It is immune to every clock problem. Timestamp carries the device clock frame plus, for CMTrace-derived events, the writing process's timezone belief. EvaluateAppInstallDurationCondition and EvaluateEventCorrelationCondition both ordered by Timestamp and expressed "A happened before B" as a timestamp comparison. Both now order by Sequence and compare Sequence for ordering. Timestamp deliberately stays where an actual ELAPSED DURATION is meant: durationSeconds, the evidence fields, and TimeWindowSeconds. Scope, honestly: this is hardening, not a live bug fix. BuiltInAnalyzeRules.cs contains zero event_correlation conditions, so the cross-frame join can only be reached by a self-authored rule. And the app-install duration evaluator pairs app_install_started with app_install_completed — both IME-sourced, one frame — so its arithmetic was already correct. (The measured 68-vs-8-minute inflation comes from EventIngestProcessor.AppInstall, which folds DO-collector download_progress together with IME app_install_completed; that is fixed at the root in the agent.) The TimeWindowSeconds check stays exposed: the window IS a duration, so there is no alternative to a timestamp there. A +1 h skew on B makes any window below 3600 s fail to match. Only the agent-side calibration closes that. Co-Authored-By: Claude Opus 5 (1M context) <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.