Oliver Kieselbach
cff765f544
Previous fix slimmed evidence + added a size guard, deployed (47ffb348), did NOT solve the real problem. Re-queueing the poison message after deploy hit the same StoreRuleResultAsync false return — but the App Insights exception trail this time exposed the actual underlying error: Newtonsoft.Json.JsonSerializationException: Self referencing loop detected with type 'System.Collections.Generic.Dictionary<String,Object>'. Path 'enforcement_error_resolved.allMatches'. Pre-existing latent bug in EvaluateEventCorrelationCondition since v1: matchedPairs[0] IS primary by reference. primary["allMatches"] = matchedPairs (or a Take(N).ToList() slice that still contains the same reference) creates primary -> allMatches[0] -> primary, which Newtonsoft refuses to serialize. JsonConvert.SerializeObject throws inside StoreRuleResultAsync, the catch returns false, and the queue handler propagates a retry — eventually hitting poison after 5 attempts. Why this never fired before: correlation rules typically produce 0 or 1 match, and the if (matchedPairs.Count > 1) branch was dead code in production. The 12-day stuck session that surfaced this was the first real session with multiple correlated app_install_failed/completed pairs. Fix: clone each pair into a new Dictionary<string, object> when populating allMatches. The clones are independent instances with the same data, so Newtonsoft sees them as distinct objects and the cycle is broken. Pair flat-clone is sufficient — pairs only contain primitive values + small strings, no nested dicts. Also kept: the slim evidence (no message, no errorDetail) and the 60KB size guard from47ffb348. Both still good defense-in-depth — the size guard never got a chance to trigger before because serialize threw first. Test: RuleEngineCorrelationEvidenceSlimTests.Correlation_with_multiple_pairs_serializes_without_self_referencing_loop runs JsonConvert.SerializeObject(MatchedConditions) end-to-end and fails fast if the loop sneaks back in. 774/774 backend pass. Co-Authored-By: Claude Opus 4.7 (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.