Oliver Kieselbach
eca528b9b3
The boot marks answered the question on the first production cold start, and the answer overturns the reasoning behind an infrastructure change made earlier today. +244ms node started (startup + module loading) +431ms corpora read from disk (+187ms) +491ms index read, validated, hydrated (+60ms for 3.12 MB) +504ms listening +677ms query embedder warm (background) Against a 31.5s cold start, the application accounts for half a second. The other ~98% is Container Apps activation: KEDA reacting, pod scheduling, mounting the 236 MB image, starting the container. The container also boots faster than a development laptop (504ms vs 1273ms), so nothing here is CPU-starved. Consequences recorded rather than quietly dropped: - Raising the container to 0.5 vCPU was justified by the embedding model load on the cold-start path. Prebaked, that load is 173ms and runs in the background where only the first search could wait on it. The justification does not survive measurement. The setting stays — it plausibly helps concurrent requests, and at scale-to-zero the cost difference is negligible — but the Bicep comment now says what is true instead of what was assumed, so nobody re-derives the wrong reason. - Index size is irrelevant to startup (60ms for 3.12 MB), so the corpus can grow freely, and the embedding rounding earns its keep on file size alone. - The only lever that would actually remove the cold start is minReplicas: 1, at roughly 7x the monthly free consumption grant. Co-Authored-By: Claude Opus 4.8 (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.
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 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.