Tenant observability package
The HCS tenant observability package is a reusable, cost-first Azure Monitor and FinOps foundation. It is the canonical implementation for Platform Engineering work item AB#6276. Workloads such as Homestead Foundry consume it through public configuration and private deployment overlays.
What a complete operating view answers
| Question | Azure-native evidence | Initial cost posture |
|---|---|---|
| What is spending and where is it trending? | Cost Management budgets, cost analysis, anomaly detection, exports, and tag allocation | Native Cost Management first |
| What is deployed, who owns it, and is it temporary? | Azure Resource Graph and the tag contract | Metadata only |
| What changed or failed? | Activity Log, deployment history, selected Activity Log alerts | Activity Log first; export only when justified |
| Is Azure affecting the workload? | Service Health, Resource Health, and action groups | Narrow, low-noise alerts |
| Is a workload behaving normally? | Azure Monitor standard metrics and targeted metric alerts | Standard metrics before log ingestion |
| Why did a request, agent, or dependency fail? | Approved diagnostic categories and Application Insights tracing | Gated for data classification and cost |
| Who responds and what happens next? | Action groups, alert processing rules, severity policy, and runbooks | Required for every enabled alert |
| Can the view extend to Azure Local and Foundry Local? | Azure Local standard metrics, Arc, managed Prometheus, and opt-in local metadata | Deferred until a hybrid workload exists |
Documents
- Architecture: product boundary, 360-degree capability model, WAF and CAF decisions.
- Implementation: module layout, deployment lifecycle, dashboards, queries, and profile enablement.
- Operations: alert response, cost controls, tag governance, changes, and incident handling.
- Parameter reference: every public Bicep input and private-overlay rule.
Consumption rule
Platform owns the reusable package. A workload repository may add a configuration example, an alert-definition file, or a dashboard definition that it needs, but it must not fork the package or send private values back upstream. Improvements that are generally reusable are made here first, then pulled into the workload repository.