Azure Monitor health models for Azure Local
Azure Local / Azure Monitor — the committed Azure Monitor delivery surface for Azure Local.
This section covers how the Azure Local design is implemented as an Azure Monitor Health Model. Read the Azure Local Azure Monitor design lane first. Its entity graph, DCMA signals, cloud prerequisites, and deployment model do not govern Hyper-V.
Start with the prerequisites
Before building or deploying the health model, work through the prerequisites. The model itself collects nothing; it consumes signals from HCI Insights, Azure Monitor Agent, Telemetry and Diagnostics, and Resource Health.
Preview development baseline
The Health Model resource graph, identity, entities, relationships, two documented Azure Local metric signals, parameter files, research KQL, workbook, and compile-time contract test are implemented. The service and APIs remain preview. Live deployment and fault evidence are required before release.
Hyper-V is monitored exclusively on-premises via System Center Operations Manager (SCOM) and has zero Azure Monitor dependencies.
What lives here
| Page | Content |
|---|---|
| Prerequisites | Cloud-side setup contract (HCI Insights, AMA, DCMA, RBAC, networking) |
| Architecture | Current resource, entity, signal, identity, and validation architecture |
| Research | Revalidated API/signal evidence and remaining spikes |
| Entities | Deployment, six domain entities, cluster Azure-resource entity, and dependency relationships |
| Signals | Two documented Azure Local metric definitions; KQL remains research-only until schemas are proven |
| Alerts | Parameterized deployment-level Degraded and Unhealthy state alerts |
| Bicep modules | Azure Monitor account, Health Model, authentication, signals, entities, and relationships |
| Workbook | Starter Azure Local investigation workbook |
| Diagrams | Entity graph (Mermaid + draw.io), health propagation flow |
Where to start
- Prerequisites — make sure your cloud side is wired up
- Azure Local Azure Monitor design — the governing lane
- Azure Monitor entity model ADR
- Cloud prerequisites contract ADR
- Customization — how operators tune the Azure Monitor track
Development and release boundary
- Bicep build and repository contract checks run without an Azure subscription.
- Service Group discovery remains a research item; the initial model uses explicit entities.
- Customer resource IDs and Action Groups are parameters, never committed values.
- Live what-if, deployment, RBAC, signal evaluation, fault/recovery, cost, and teardown are mandatory pre-release evidence.