Oliver Kieselbach
b9fa760404
The per-line self-anchoring provenance (sourceLocalTs, applied offset + origin, observational writer offset, derived/rejected markers) reaches the browser but was buried unlabeled in the raw JSON dump. Sequence stays THE sort order - without exception (now pinned by a regression test); the corrected UTC is display-only, and a backwards step of the displayed time within sequence order is marked as information instead of confusing the reader. - lib/timeProvenance.ts: readTimeProvenance (camelCase/snake_case, tolerant of truncated payloads) + classifyTimeJump with cause precedence derived > rejected-source > era-offset; era-offset requires applied offsets on BOTH rows - it never guesses. - TimeJumpBadge on the row AFTER the jump, computed against the previous RENDERED row (filters/phase boundaries respected); sky for known causes, amber otherwise; tooltip carries both times, the delta and the "true write order (sequence)" sentence. Threshold 5 min, field-calibrated on 20 sessions: 12/12 normal sessions show zero badges, the era-mixed regression session shows exactly its 6. - Clamped chip (rare) + TIME PROVENANCE detail section: only the applied offset says "(applied)"; the writer offset is explicitly observational (sticky after era flip-backs); origin chips with forward-compatible fallback for unknown values. - EnrollmentEvent gains timestampClamped/originalTimestamp (wire already carried them); formatUtcOffset joins lib/formatting. Verified: 814 web tests (19 new), tsc/eslint/build clean; Playwright against e9753578 (badges match the pre-measurement), 9f475bb2 (no badge on line-anchored rows, detail section correct, raw mode shows exactly the one predicted jump). 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.