Learn / Labs / Tools

Observability & Evidence

Monitoring, logging, telemetry, reporting, reconciliation, validation, maintenance evidence, handoff, and audit-oriented operational proof.

0 guides4 labs10 tools1 capability mapsBrowse all topic paths

Capability Maps

How this path becomes useful work

01

Learn

Understand Observability & Evidence

Technical guides that explain the concepts, architecture, decisions, and durable operator patterns.

This Learn path is intentionally open for new technical guides.

02

Labs

Practice Observability & Evidence

Hands-on labs that turn the concepts into working systems and repeatable environments.

03

Tools

Operate Observability & Evidence

Free operator tools for checks, scripts, evidence, reporting, and practical infrastructure work.

Azure Update Manager compliance workbook starterStarter template for an Azure Workbook plus Resource Graph evidence pack that shows patch compliance, pending updates, unsupported coverage, and patch-group drift across Azure and Arc-enabled machines.TemplateReporting and Evidence PacksRead-onlyBuild the Ops Reporting Foundation HelperCreate the local PowerShell helper file that every Ops Stack reporting-compatible script can share. This guide walks through the folder structure, the helper contract, the commented PowerShell implementation, a sample validation run, and the artifacts the helper creates so a new reader can build it from scratch and prove it works.TemplateReporting and Evidence PacksChanges system stateIncident Note TemplateA compact operator note format for capturing symptoms, checks, decisions, and follow-up while the issue is fresh.TemplateOperations TemplatesPlanning aidInstalled Application Inventory for Windows EndpointsA read-only PowerShell inventory starter for collecting installed applications from local or remote Windows endpoints.ScriptInventoryRead-onlyInternal URL monitoring deployment and trust runbookOne authoritative path for monitoring 10–20 internal HTTP/HTTPS endpoints: define endpoint semantics, deploy Uptime Kuma, set retry and maintenance policy, add TLS/auth checks, alert, retain history, and prove the monitor with a controlled outage.ChecklistMonitoring and ObservabilityPlanning aidPatch compliance Prove the Number monthly evidence packA ready-to-fill monthly record that turns patch-compliance methodology into a defensible reporting package: population reconciliation, denominator rules, unknown/stale systems, exclusions, applicability, evidence coverage, exceptions, signoff, and management summary.TemplateReporting and Evidence PacksPlanning aidPowerShell HTML operations report starterConcrete PowerShell reporting pattern for turning host-check results into an HTML operations summary with a status rollup, per-host table, failure section, saved local artifacts, and optional email delivery.TemplateReporting and Evidence PacksChanges system statePowerShell operations reporting foundationUse the Ops Reporting Foundation helper to turn PowerShell checks into consistent HTML, CSV, JSON, and log artifacts. Start here after creating the helper file, then plug health checks, patch checks, certificate scans, AD hygiene checks, and other collectors into the same reporting pattern.TemplateReporting and Evidence PacksReview before runningRADIUS and NPS server detection reportRead-only PowerShell reporting script pattern to identify likely Microsoft NPS or other RADIUS-capable Windows servers using multiple evidence sources: NPS service presence, NPAS role/feature state, IAS/NPS event log activity, UDP 1812/1813 listener evidence, and registry indicators. Designed for migration discovery, audit support, and authentication troubleshooting.ScriptInventoryRead-onlyUptime Kuma Monitoring StarterA simple monitoring starter for internal services, homelab systems, and small-office status checks.Recommended toolMonitoringChanges system state