Oliver Kieselbach 428b14cd60 v2 single-rail 4.3: add InformationalEventPost helper for signal posting
Introduce the migration helper that lets peripheral collectors post an
InformationalEvent signal without assembling the payload dict, the
evidence record, or the signal kind themselves. Every PR #1-#9 call
site in the single-rail refactor will go through this helper instead
of writing raw TelemetryEventEmitter.Emit calls.

- InformationalEventPost in V2.Core.Orchestration, constructor takes
  ISignalIngressSink + IClock (matches the existing adapter pattern).
- Emit(eventType, source, ...) writes eventType + source mandatorily and
  folds optional message / severity / immediateUpload / phase / data
  into the payload using SignalPayloadKeys constants.
- Data entries that collide with reserved top-level keys are silently
  dropped so a caller-supplied "source" in data cannot rewrite the
  explicit source label on the wire.
- Evidence summary falls back to explicit arg → message → eventType in
  that order.
- Timestamp defaults to IClock.UtcNow; callers can override via
  occurredAtUtc for deterministic replay harnesses.

13 xUnit tests cover payload composition, optional-field omission,
data-collision guard, sourceOrigin/evidence fallback chain, argument
validation, and timestamp semantics with VirtualClock.

The helper lives outside Telemetry.Events so it stays reachable from
callers once TelemetryEventEmitter becomes internal in PR #10
(enforcement step).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-23 13:01:24 +02:00
2026-04-22 19:36:19 +02:00
2026-04-22 19:36:19 +02:00
2026-03-17 18:24:01 +01:00
2026-03-26 07:02:33 +01:00
2026-04-04 19:17:01 +02:00

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.

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%