Merge pull request #226902 from bwren/vm-arg

Resource Graph VM availability

Author: Stacyrch140

articles/azure-monitor/toc.yml

@@ -324,24 +324,24 @@ items:
     - name: Troubleshoot
       items:
       - name: Linux VM
-        href: agents/azure-monitor-agent-troubleshoot-linux-vm.md
+        href: agents/azure-monitor-agent-troubleshoot-linux-vm.md?context=/azure/virtual-machines/context/context
       - name: Linux Rsyslog issues
-        href: agents/azure-monitor-agent-troubleshoot-linux-vm-rsyslog.md
+        href: agents/azure-monitor-agent-troubleshoot-linux-vm-rsyslog.md?context=/azure/virtual-machines/context/context
       - name: Windows VM
-        href: agents/azure-monitor-agent-troubleshoot-windows-vm.md
+        href: agents/azure-monitor-agent-troubleshoot-windows-vm.md?context=/azure/virtual-machines/context/context
       - name: Windows Arc-enabled server
-        href: agents/azure-monitor-agent-troubleshoot-windows-arc.md
+        href: agents/azure-monitor-agent-troubleshoot-windows-arc.md?context=/azure/virtual-machines/context/context
       - name: Troubleshoot legacy Agents
         displayName: Troublshooting guidance
         items:  
           - name: Log Analytics VM Extension
             displayName: troubleshoot, troubleshooting
-            href: visualize/vmext-troubleshoot.md
+            href: visualize/vmext-troubleshoot.md?context=/azure/virtual-machines/context/context
           - name: Log Analytics Windows agent
             displayName: troubleshoot, troubleshooting
-            href: agents/agent-windows-troubleshoot.md
+            href: agents/agent-windows-troubleshoot.md?context=/azure/virtual-machines/context/context
           - name: Log Analytics Linux agent
-            displayName: troubleshoot, troubleshooting
+            displayName: troubleshoot, troubleshooting?context=/azure/virtual-machines/context/context
             href: agents/agent-linux-troubleshoot.md
   - name: Logs ingestion API
     items:

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

@@ -146,76 +146,6 @@ For instructions on how to create your own custom workbooks, see [Create interac
 :::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":::
 
 
-## VM availability information in Azure Resource Graph
-[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:
-
-- Query the latest snapshot of VM availability together across all your Azure subscriptions. 
-- Assess the impact to business SLAs and trigger decisive mitigation actions, in response to disruptions and type of failure signature.
-- 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.
-- 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.
-
-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.
-
-:::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" :::
-
-To view the details for a record, scroll to the right and select **See details**.
-
-:::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" :::
-
-There will be two  types of events populated in the HealthResources table:
-
-### microsoft.resourcehealth/availabilitystatuses
-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:
-
-- **Available**: The VM is up and running as expected.
-- **Unavailable**: A disruption to the normal functioning of the VM has been detected.
-- **Unknown**: The platform is unable to accurately detect the health of the VM. Check back in a few minutes.
-
-The availability state is in the `properties` field of the record which includes the following properties:
-
-| Field | Description |
-|:---|:---|
-| targetResourceType | Type of resource for which health data is flowing |
-| targetResourceId | Resource ID |
-| occurredTime | Timestamp when the latest availability state is emitted by the platform |
-| previousAvailabilityState | Previous availability state of the VM |
-| availabilityState | Current availability state of the VM |
-
-A sample `properties` value looks similar to the following:
-
-```json
-{
-    "targetResourceType": "Microsoft.Compute/virtualMachines",
-    "previousAvailabilityState": "Available",
-"targetResourceId": "/subscriptions/<subscriptionId>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Compute/virtualMachines/<VMName>",
-    "occurredTime": "2022-10-11T11:13:59.9570000Z",
-    "availabilityState": "Unavailable"
-}
-
-```
-
-### microsoft.resourcehealth/resourceannotations
-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).
-
-These annotations can be broadly classified into the following:
-
-- **Downtime Annotations**: Emitted when the platform detects VM availability transitioning to Unavailable. Examples include host crashes or reboot operations.
-- **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.
-- **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.
-
-| Field | Description |
-|:---|:---|
-| targetResourceType | Type of resource for which health data is flowing |
-| targetResourceId | Resource ID |
-| occurredTime | Timestamp when the latest availability state is emitted by the platform |
-| annotationName | Name of the Annotation emitted |
-| reason | Brief overview of the availability impact observed by the customer |
-| 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 |
-| 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 |
-| summary | Statement detailing the cause for annotation emission, along with remediation steps that can be taken by users |
-
-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.
-
 ## Next steps
 
 * [Create alerts from collected data](monitor-virtual-machine-alerts.md)

articles/virtual-machines/TOC.yml

@@ -984,14 +984,6 @@
         href: ../azure-monitor/agents/azure-monitor-agent-manage.md?context=/azure/virtual-machines/context/context
       - name: Diagnostics extension
         href: ../azure-monitor/agents/diagnostics-extension-overview.md?context=/azure/virtual-machines/context/context
-      - name: Log Analytics
-        items:
-        - name: Linux
-          displayName: Log Analytics, extension
-          href: ./extensions/oms-linux.md
-        - name: Windows
-          displayName: Log Analytics, extension
-          href: ./extensions/oms-windows.md
       - name: VM insights
         items:
         - name: Linux Dependency agent
@@ -1000,6 +992,16 @@
         - name: Windows Dependency agent
           displayName: Azure Monitor
           href: ./extensions/agent-dependency-windows.md
+      - name: Legacy extensions
+        items:
+        - name: Log Analytics
+          items:
+          - name: Linux
+            displayName: Log Analytics, extension
+            href: ./extensions/oms-linux.md
+          - name: Windows
+            displayName: Log Analytics, extension
+            href: ./extensions/oms-windows.md
     - name: PowerShell DSC
       href: ./extensions/dsc-overview.md
       items:
@@ -1839,129 +1841,38 @@
     href: monitor-vm.md?context=/azure/virtual-machines/context/context
   - name: Monitor virtual machine reference
     href: monitor-vm-reference.md?context=/azure/virtual-machines/context/context
+  - name: Availability with Resource Graph
+    href: resource-graph-availability.md
   - name: Tutorials
     items:
-    - name: Enable monitoring
-      href: ../azure-monitor/vm/tutorial-monitor-vm-enable.md?context=/azure/virtual-machines/context/context
-    - name: Alert on machine down
-      href: ../azure-monitor/vm/tutorial-monitor-vm-alert.md?context=/azure/virtual-machines/context/context
+    - name: Enable recommended alerts
+      href: ../azure-monitor/vm/tutorial-monitor-vm-alert-recommended.md?context=/azure/virtual-machines/context/context
+    - name: Create availability alert
+      href: ../azure-monitor/vm/tutorial-monitor-vm-alert-availability.md?context=/azure/virtual-machines/context/context
+    - name: Enable VM insights
+      href: ../azure-monitor/vm/tutorial-monitor-vm-enable-insights.md?context=/azure/virtual-machines/context/context
     - name: Collect guest logs and metrics
       href: ../azure-monitor/vm/tutorial-monitor-vm-guest.md?context=/azure/virtual-machines/context/context
-  - name: Agents
+  - name: Monitor virtual machines guide
     items:
-    - name: Agents overview
-      href: ../azure-monitor/agents/agents-overview.md?context=/azure/virtual-machines/context/context
-    - name: FAQ
-      displayName: Agents
-      href: ../azure-monitor/faq.yml
-    - name: Azure Monitor Agent
-      items:
-      - name: Overview
-        href: ../azure-monitor/agents/azure-monitor-agent-overview.md?context=/azure/virtual-machines/context/context
-        displayname: Azure Monitor agent
-      - name: Install and manage
-        href: ../azure-monitor/agents/azure-monitor-agent-manage.md?context=/azure/virtual-machines/context/context
-        displayname: Azure Monitor agent
-      - name: Data collection
-        href: ../azure-monitor/agents/data-collection-rule-azure-monitor-agent.md?context=/azure/virtual-machines/context/context
-        displayname: data collection rule,Azure Monitor agent
-      - name: Migrate from legacy agents
-        href: ../azure-monitor/agents/azure-monitor-agent-migration.md?context=/azure/virtual-machines/context/context
-        displayname: Migrate to Azure Monitor agent
-      - name: FAQ
-        href: ../azure-monitor/faq.yml?context=/azure/virtual-machines/context/context
-        displayname: Azure Monitor agent FAQ
-    - name: Log Analytics agent
-      items:
-      - name: Overview
-        displayName: Log Analytics Agent
-        href: ../azure-monitor/agents/log-analytics-agent.md?context=/azure/virtual-machines/context/context
-      - name: Linux agents
-        href: ../azure-monitor/agents/agent-linux.md?context=/azure/virtual-machines/context/context
-      - name: Log Analytics gateway
-        href: ../azure-monitor/agents/gateway.md?context=/azure/virtual-machines/context/context
-      - name: Agent management
-        href: ../azure-monitor/agents/agent-manage.md?context=/azure/virtual-machines/context/context
-      - name: Agent Health
-        href: ../azure-monitor/insights/solution-agenthealth.md?context=/azure/virtual-machines/context/context
-      - name: Data sources
-        items:
-        - name: Overview
-          displayName: Data sources, log Analytics
-          href: ../azure-monitor/agents/agent-data-sources.md?context=/azure/virtual-machines/context/context
-        - name: Custom JSON data
-          displayName: Data sources, log Analytics
-          href: ../azure-monitor/agents/data-sources-json.md?context=/azure/virtual-machines/context/context
-        - name: collect performance data
-          displayName: Data sources, log Analytics
-          href: ../azure-monitor/agents/data-sources-collectd.md?context=/azure/virtual-machines/context/context
-        - name: Syslog
-          displayName: Data sources, log Analytics
-          href: ../azure-monitor/agents/data-sources-syslog.md?context=/azure/virtual-machines/context/context
-        - name: Performance counters
-          displayName: Data sources, log Analytics
-          href: ../azure-monitor/agents/data-sources-performance-counters.md?context=/azure/virtual-machines/context/context
-        - name: Linux application performance
-          displayName: Data sources, log Analytics
-          href: ../azure-monitor/agents/data-sources-linux-applications.md?context=/azure/virtual-machines/context/context
-        - name: Custom logs
-          displayName: Data sources, log Analytics
-          href: ../azure-monitor/agents/data-sources-custom-logs.md?context=/azure/virtual-machines/context/context
-        - name: Custom fields
-          displayName: Data sources, log Analytics
-          href: ../azure-monitor/logs/custom-fields.md?context=/azure/virtual-machines/context/context
-    - name: Troubleshoot
-      items:
-      - name: Log Analytics VM Extension
-        href: ../azure-monitor/visualize/vmext-troubleshoot.md?context=/azure/virtual-machines/context/context
-      - name: Log Analytics Linux agent
-        href: ../azure-monitor/agents/agent-linux-troubleshoot.md?context=/azure/virtual-machines/context/context
-    - name: VM insights
-      items:
-      - name: Overview
-        displayName: VM insights
-        href: ../azure-monitor/vm/vminsights-overview.md?context=/azure/virtual-machines/context/context
-      - name: FAQ
-        displayName: VM insights
-        href: ../azure-monitor/faq.yml?context=/azure/virtual-machines/context/context
-      - name: Enable monitoring
-        items:
-        - name: Enable monitoring overview
-          displayName: Azure monitor, monitoring
-          href: ../azure-monitor/vm/vminsights-enable-overview.md?context=/azure/virtual-machines/context/context
-        - name: Enable for single Azure VM
-          displayName: Azure monitor, monitoring
-          href: ../azure-monitor/vm/vminsights-enable-portal.md?context=/azure/virtual-machines/context/context
-        - name: Enable using Azure Policy
-          displayName: Azure monitor, monitoring
-          href: ../azure-monitor/vm/vminsights-enable-policy.md?context=/azure/virtual-machines/context/context
-        - name: Enable using Azure PowerShell
-          displayName: Azure monitor, monitoring
-          href: ../azure-monitor/vm/vminsights-enable-powershell.md?context=/azure/virtual-machines/context/context
-        - name: Enable for Hybrid environment
-          displayName: Azure monitor, monitoring
-          href: ../azure-monitor/vm/vminsights-enable-hybrid.md?context=/azure/virtual-machines/context/context
-      - name: Map dependencies
-        displayName: Azure monitor, monitoring
-        href: ../azure-monitor/vm/vminsights-maps.md?context=/azure/virtual-machines/context/context
-      - name: Monitor performance
-        displayName: Azure monitor, monitoring
-        href: ../azure-monitor/vm/vminsights-performance.md?context=/azure/virtual-machines/context/context
-      - name: Analyze data with log queries
-        displayName: Azure monitor, monitoring
-        href: ../azure-monitor/vm/vminsights-log-query.md
-      - name: Visualize data with workbooks
-        displayName: Azure monitor, monitoring
-        href: ../azure-monitor/vm/vminsights-workbooks.md?context=/azure/virtual-machines/context/context
-      - name: Create alert rules
-        displayName: Azure monitor, monitoring
-        href: ../azure-monitor/vm/monitor-virtual-machine-alerts.md?context=/azure/virtual-machines/context/context
-      - name: Upgrade Dependency agent
-        displayName: Azure monitor, monitoring
-        href: ../azure-monitor/vm/vminsights-dependency-agent-maintenance.md?context=/azure/virtual-machines/context/context
-      - name: Disable monitoring
-        displayName: Azure monitor, monitoring
-        href: ../azure-monitor/vm/vminsights-optout.md?context=/azure/virtual-machines/context/context
+    - name: Overview
+      href: ../azure-monitor/vm/monitor-virtual-machine.md
+    - name: Deploy agents
+      href: ../azure-monitor/vm/monitor-virtual-machine-agent.md
+    - name: Collect data
+      href: ../azure-monitor/vm/monitor-virtual-machine-data-collection.md
+    - name: Analyze data
+      href: ../azure-monitor/vm/monitor-virtual-machine-analyze.md
+    - name: Create alerts
+      href: ../azure-monitor/vm/monitor-virtual-machine-alerts.md
+    - name: Migrate management pack logic
+      href: ../azure-monitor/vm/monitor-virtual-machine-management-packs.md
+  - name: VM insights
+    href: ../azure-monitor/vm/vminsights-overview.md
+  - name: Azure Monitor Agent
+    href: ../azure-monitor/agents/agents-overview.md
+  - name: Analyze availability
+    href: resource-graph-availability.md
   - name: VM usage
     href: vm-usage.md
   - name: Tag a VM