Oliver Kieselbach
e9dba11b96
This is the behaviour change the previous two commits prepared. ImeLogTracker no longer substitutes its own timezone belief for the IME process's; it measures the writer's offset from a freshly appended line and converts with that. Freshness is stricter than "the file grew". GetSafePosition returns 0 for an unknown file, so the first pass reads the whole file and its newest line may be hours old — anchoring there would measure the line's age, not the writer's offset. LogFilePositionTracker.HasSeen(), captured BEFORE GetSafePosition creates the entry, gates calibration on growth against a size we had already observed. Calibration runs at the END of a qualifying pass, so that pass still uses the previously measured offset — at most one poll (100 ms) old, and an offset only moves when a process restarts. Calibrating first would mean buffering the pass, which is not viable: the first pass over AppWorkload.log can be hundreds of MB. The cost is a warm-up of one growing pass, during which lines fall back to the reader zone. Bias-carrying lines are never used as anchors: they already state the writer's offset, so they need no measurement and must not overwrite one. CalibrateFrom logs at Info when the measured offset disagrees with this process's own zone, naming the correction applied. That disagreement is precisely the condition that silently corrupted every IME-derived timestamp until now; agreement stays at Debug so the normal case does not add noise. Tests are deliberately machine-independent: the assertion is always "a line written at instant T resolves to T", asserted across writer beliefs of +2, +1, 0, -7 and +10. That one property covers both field cases — the writer disagreeing with us (the bug) and the writer agreeing with us (the majority of sessions, where two stale beliefs cancel and which a fix to the agent's own cache would have broken). Plus: no calibration on first sight, following a writer restart into a new zone, and a declared bias honoured without being measured. CheckLogFilesAsync is internal as a test seam — calibration depends on the pass structure, which only a real read cycle exercises. Agent 2390 / backend 4313 green against a verified-clean build. 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.