SCOM Management Pack¶
Track 1 — SCOM health monitoring for Azure Local clusters.
This section covers how the design is implemented as a SCOM Management Pack. The design itself — entity model, signal catalog, rollup policy, customization — is track-agnostic and lives in Design. Read that first.
Phase 3 — coming after Phase 2 sign-off
Authoring lands in Phase 3 once the Design ADRs move from Proposed to Accepted. Current roadmap is in PLAN.md.
What lives here¶
| Page (planned) | Content |
|---|---|
| Health model XML overview | The sealed AzureLocal.HealthModel.mp structure |
| Class hierarchy reference | Implementation of ADR 0005 |
| Discoveries reference | PowerShell discovery scripts per ADR 0004 |
| Monitor inventory | Unit / Aggregate / Dependency monitors mapping to the Signal Catalog |
| Override pack reference | Customer-facing overrides per ADR 0008 |
| Authoring guide | VSAE + Kevin Holman fragment library workflow |
| Lifecycle | Sealing, signing, import, update, retirement |
| Diagrams | Health rollup tree (Mermaid) + class hierarchy (draw.io) |
Where to start¶
- Design overview — the conceptual foundation
- SCOM class hierarchy ADR
- Discovery strategy ADR
- Customization — how operators tune the SCOM track
Track-specific upstream references¶
- Brian Wren / MPAuthor video series (SC 2012 R2 — Operations Manager Management Packs)
- Kevin Holman — SCOM Management Pack Fragment Library
- Silect MP Author (free authoring tool)
- See full reference list in REFERENCES.md.