Skip to content

Commit 54a1000

Browse files
bwrenbwren
committed
fixes
1 parent 9fcf993 commit 54a1000

File tree

2 files changed

+2
-72
lines changed

2 files changed

+2
-72
lines changed

‎articles/azure-monitor/vm/monitor-virtual-machine-analyze.md

Lines changed: 0 additions & 70 deletions
Original file line numberDiff line numberDiff line change
@@ -146,76 +146,6 @@ For instructions on how to create your own custom workbooks, see [Create interac
146146
:::image type="content" source="media/monitor-virtual-machines/workbook-example.png" alt-text="Screenshot that shows virtual machine workbooks." lightbox="media/monitor-virtual-machines/workbook-example.png":::
147147

148148

149-
## VM availability information in Azure Resource Graph
150-
[Azure Resource Graph](../../governance/resource-graph/overview.md) is an Azure service that allows you to use the same KQL query language used in log queries to query your Azure resources at scale with complex filtering, grouping, and sorting by resource properties. You can use [VM health annotations](../../service-health/resource-health-vm-annotation.md) to Azure Resource Graph (ARG) for detailed failure attribution and downtime analysis including the following:
151-
152-
- Query the latest snapshot of VM availability together across all your Azure subscriptions.
153-
- Assess the impact to business SLAs and trigger decisive mitigation actions, in response to disruptions and type of failure signature.
154-
- Set up custom dashboards to supervise the comprehensive health of applications by [joining](../../governance/resource-graph/concepts/work-with-data.md) VM availability information with additional [resource metadata](../../governance/resource-graph/samples/samples-by-table.md?tabs=azure-cli) in Resource Graph.
155-
- Track relevant changes in VM availability across a rolling 14 days window, by using the [change tracking](../../governance/resource-graph/how-to/get-resource-changes.md) mechanism for conducting detailed investigations.
156-
157-
To get started with Resource Graph, open **Resource Graph Explorer** in the Azure portal. Select the **Table** tab and have a look at the [microsoft.resourcehealth/availabilitystatuses](#microsoftresourcehealthavailabilitystatuses) and [microsoft.resourcehealth/resourceannotations](#microsoftresourcehealthresourceannotations) tables which are described below. Click on **healthresources** to create a simple query and then click **Run** to return the records.
158-
159-
:::image type="content" source="media/monitor-virtual-machines/resource-graph-explorer-healthresources.png" alt-text="Screenshot of Azure Resource Graph with simple healthresources query." lightbox="media/monitor-virtual-machines/resource-graph-explorer-healthresources.png" :::
160-
161-
To view the details for a record, scroll to the right and select **See details**.
162-
163-
:::image type="content" source="media/monitor-virtual-machines/resource-graph-explorer-healthresources-detail.png" alt-text="Screenshot of Azure Resource Graph healthresources detailed record." lightbox="media/monitor-virtual-machines/resource-graph-explorer-healthresources-detail.png" :::
164-
165-
There will be two types of events populated in the HealthResources table:
166-
167-
### microsoft.resourcehealth/availabilitystatuses
168-
This event denotes the latest availability status of a VM, based on the [health checks](../../service-health/resource-health-checks-resource-types.md#microsoftcomputevirtualmachines) performed by the underlying Azure platform. The [availability states](../../service-health/resource-health-overview.md#health-status) currently emitted for VMs are as follows:
169-
170-
- **Available**: The VM is up and running as expected.
171-
- **Unavailable**: A disruption to the normal functioning of the VM has been detected.
172-
- **Unknown**: The platform is unable to accurately detect the health of the VM. Check back in a few minutes.
173-
174-
The availability state is in the `properties` field of the record which includes the following properties:
175-
176-
| Field | Description |
177-
|:---|:---|
178-
| targetResourceType | Type of resource for which health data is flowing |
179-
| targetResourceId | Resource ID |
180-
| occurredTime | Timestamp when the latest availability state is emitted by the platform |
181-
| previousAvailabilityState | Previous availability state of the VM |
182-
| availabilityState | Current availability state of the VM |
183-
184-
A sample `properties` value looks similar to the following:
185-
186-
```json
187-
{
188-
"targetResourceType": "Microsoft.Compute/virtualMachines",
189-
"previousAvailabilityState": "Available",
190-
"targetResourceId": "/subscriptions/<subscriptionId>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Compute/virtualMachines/<VMName>",
191-
"occurredTime": "2022-10-11T11:13:59.9570000Z",
192-
"availabilityState": "Unavailable"
193-
}
194-
195-
```
196-
197-
### microsoft.resourcehealth/resourceannotations
198-
This event contextualizes any changes to VM availability, by detailing necessary failure attributes to help you investigate and mitigate the disruption as needed. The full list of VM health annotations are listed at [Resource Health virtual machine Health Annotations] (../../service-health/resource-health-vm-annotation.md).
199-
200-
These annotations can be broadly classified into the following:
201-
202-
- **Downtime Annotations**: Emitted when the platform detects VM availability transitioning to Unavailable. Examples include host crashes or reboot operations.
203-
- **Informational Annotations**: Emitted during control plane activities with no impact to VM availability. Examples include VM allocation, stop, delete, start. Usually, no additional customer action is required in response.
204-
- **Degraded Annotations**: Emitted when VM availability is detected to be at risk. Examples include when failure prediction models predict a degraded hardware component that can cause the VM to reboot at any given time. You should redeploy by the deadline specified in the annotation message to avoid any unanticipated loss of data or downtime.
205-
206-
| Field | Description |
207-
|:---|:---|
208-
| targetResourceType | Type of resource for which health data is flowing |
209-
| targetResourceId | Resource ID |
210-
| occurredTime | Timestamp when the latest availability state is emitted by the platform |
211-
| annotationName | Name of the Annotation emitted |
212-
| reason | Brief overview of the availability impact observed by the customer |
213-
| category | Denotes whether the platform activity triggering the annotation was either planned maintenance or unplanned repair. This field is not applicable to customer/VM-initiated events.<br><br>Possible values: Planned \| Unplanned \| Not Applicable \| Null |
214-
| context | Denotes whether the activity triggering the annotation was due to an authorized user or process (customer initiated), or due to the Azure platform (platform initiated) or even activity in the guest OS that has resulted in availability impact (VM initiated).<br><br>Possible values: Platform-Initiated \| User-initiated \|VM-initiated \| Not Applicable \| Null |
215-
| summary | Statement detailing the cause for annotation emission, along with remediation steps that can be taken by users |
216-
217-
See [Azure Resource Graph sample queries by table](../../governance/resource-graph/samples/samples-by-table.md?tabs=azure-cli#healthresources) for sample queries using this data.
218-
219149
## Next steps
220150

221151
* [Create alerts from collected data](monitor-virtual-machine-alerts.md)

‎articles/virtual-machines/resource-graph-availability.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,11 @@ ms.reviewer: Xema Pathak
2020

2121
To get started with Resource Graph, open **Resource Graph Explorer** in the Azure portal. Select the **Table** tab and have a look at the [microsoft.resourcehealth/availabilitystatuses](#microsoftresourcehealthavailabilitystatuses) and [microsoft.resourcehealth/resourceannotations](#microsoftresourcehealthresourceannotations) tables which are described below. Click on **healthresources** to create a simple query and then click **Run** to return the records.
2222

23-
:::image type="content" source="media/monitor-virtual-machines/resource-graph-explorer-healthresources.png" alt-text="Screenshot of Azure Resource Graph with simple healthresources query." lightbox="media/monitor-virtual-machines/resource-graph-explorer-healthresources.png" :::
23+
:::image type="content" source="media/monitor-vm/resource-graph-explorer-healthresources.png" alt-text="Screenshot of Azure Resource Graph with simple healthresources query." lightbox="media/monitor-vm/resource-graph-explorer-healthresources.png" :::
2424

2525
To view the details for a record, scroll to the right and select **See details**.
2626

27-
:::image type="content" source="media/monitor-virtual-machines/resource-graph-explorer-healthresources-detail.png" alt-text="Screenshot of Azure Resource Graph healthresources detailed record." lightbox="media/monitor-virtual-machines/resource-graph-explorer-healthresources-detail.png" :::
27+
:::image type="content" source="media/monitor-vm/resource-graph-explorer-healthresources-detail.png" alt-text="Screenshot of Azure Resource Graph healthresources detailed record." lightbox="media/monitor-vm/resource-graph-explorer-healthresources-detail.png" :::
2828

2929
There will be two types of events populated in the HealthResources table:
3030

0 commit comments

Comments
 (0)