Oliver Kieselbach 86f5b50778 perf(geo): parallel projected scans for geographic metrics + shared progress UX
Same pattern as the Platform Usage fix (e63a0bc2): the geographic endpoints
ran two sequential full-column window scans per request while the web app's
default 30s fetch timeout could abort the response client-side.

Backend:
- New column-projected queries: GetGeoWindowSessionsAsync ($select Geo*
  grouping fields + effective-duration inputs) and
  GetGeoAppInstallSummariesAsync ($select session join key, window filter,
  throughput inputs and all Delivery Optimization counters; returned
  AppInstallSummary objects carry only those fields by documented contract)
- All four geographic functions (tenant/global map + tenant/global location
  drilldown) run their scans concurrently via Task.WhenAll; the map
  endpoints use both projections, the drilldowns keep full-row sessions
  (LocationSessionRow returns nearly every column) but switch to the lean
  app scan
- GeoMetricsProjectionEquivalenceTests pins both projections, incl. the
  location grouping key and the DoDownloadMode=-1 "no DO telemetry" marker

Web:
- New shared useFetchProgress hook + CalculatingCard component (elapsed
  counter + progress bar sized from the last recorded fetch duration,
  capped at 95%)
- geographic-performance map + sessions drilldown: 180s AbortSignal and
  the calculating card instead of a bare loading line
- SectionPlatformUsage refactored onto the shared hook/component (drops
  its inline copy of the timer/estimate logic)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-11 12:28:17 +02:00
2026-07-10 15:53:32 +02:00
2026-03-26 07:02:33 +01:00
2026-07-06 20:53:00 +02:00

AutopilotMonitor

Status License Website

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%