--- id: azure-virtual-machine title: Azure Virtual Machine description: Learn about the Sumo Logic collection process for the Azure Virtual Machine service. slug: /help/docs/integrations/microsoft-azure/azure-virtual-machine/ canonical: https://www.sumologic.com/help/docs/integrations/microsoft-azure/azure-virtual-machine/ --- import useBaseUrl from '@docusaurus/useBaseUrl'; Azure VM icon [Azure Virtual Machine](https://learn.microsoft.com/en-us/azure/virtual-machines/) is a virtualized computing environment on Microsoft's cloud platform, that allows users to run applications and tasks on a dedicated, scalable, and on-demand basis. Azure Virtual Machine (VM) provides scalable computing capacity in the Azure Cloud. You can use Azure VM to launch as many or as few virtual servers as you need, configure security and networking, and manage storage. The Sumo Logic app for Azure VM allows you to collect your VM instance metrics and display them using predefined dashboards. The app provides dashboards to display analysis of VM instance metrics for CPU, disk, network, cache, and memory. Also, it provides detailed insights into all audit events associated with VM instances and specifically helps identify changes, errors, and user activities. ## Log and metric types For Azure Virtual Machine, you can collect the following logs and metrics: * **Activity logs**. To learn more about the different Activity log category types and schemas collected for Azure Virtual Machine, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/virtual-machines/monitor-vm-reference#activity-log). * **Virtual Machine Metrics**. These metrics are available in [Microsoft.Compute/virtualMachines, Microsoft.Compute/virtualmachineScaleSets](https://learn.microsoft.com/en-us/azure/virtual-machines/monitor-vm-reference#metrics) namespace. For more information on supported metrics and their units, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/virtual-machines/monitor-vm-reference#supported-metrics-for-microsoftcomputevirtualmachines). ## Setup Azure service sends monitoring data to Azure Monitor, which can then [stream data to Eventhub](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/stream-monitoring-data-event-hubs). Sumo Logic supports: * Logs collection from [Azure Monitor](https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-get-started) using our [Azure Event Hubs source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/). * Metrics collection using our [Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source). You must explicitly enable diagnostic settings for each Virtual Machine you want to monitor. You can forward logs to the same event hub provided they satisfy the limitations and permissions as described [here](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/diagnostic-settings?tabs=portal#destination-limitations). When you configure the event hubs source or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: `Azure/VM/ActivityLogs`, `Azure/VM/Metrics`. ### Configure collector Create a hosted collector if not already configured and tag the `tenant_name` field. You can get the tenant name using the instructions [here](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name). Make sure you create the required sources in this collector.
Azure Tag Tenant Name #### Activity logs (optional) import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; ### Configure metrics collection import MetricsSource from '../../reuse/metrics-source.md'; :::note Metric Rule `AzureObservabilityMetadataExtractionVMName` will be created automatically as a part of app installation process. This metric rule creates new dimension `vmname` for non scale set VMs. ::: ## Installing the Azure Virtual Machine app import AppInstallIndexV2 from '../../reuse/apps/app-install-index-option.md'; As part of the app installation process, the following fields will be created by default: - `tenant_name`. This field is tagged at the collector level. You can get the tenant name using the instructions [here](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name). - `location`. The region to which the resource name belongs to. - `subscription_id`. ID associated with a subscription where the resource is present. - `resource_group`. The resource group name where the Azure resource is present. - `provider_name`. Azure resource provider name (for example, Microsoft.Network). - `resource_type`. Azure resource type (for example, storage accounts). - `resource_name`. The name of the resource (for example, storage account name). - `service_type`. Type of the service that can be accessed with a Azure resource. - `service_name`. Services that can be accessed with an Azure resource (for example, in Azure Container Instances the service is Subscriptions). ## Viewing the Azure Virtual Machine dashboards import ViewDashboardsIndex from '../../reuse/apps/view-dashboards-index.md'; ### Overview The **Azure Virtual Machine - Overview** dashboard allows you to gain insights into the performance of your VMs by monitoring and analyzing your VM's usage metrics such as VM availability, CPU usage, read/write ops, cache hits, VM usage, and average latencies. Azure Virtual Machine - Overview dashboard ### OS/Disk The **Azure Virtual Machine - OS/Disk** dashboard provides details on the operational activities and status of your Azure VM OS and Data disks. Azure Virtual Machine - OS/Disk dashboard ### Network The **Azure Virtual Machine - Network** dashboard provides detailed information about VM network activities based on incoming and outgoing packets and bytes. Azure Virtual Machine - Network dashboard ### Disk The **Azure Virtual Machine - Disk** dashboard provides details on the operational activities and status of your Azure VM disks and premium disks. Azure Virtual Machine - Disk dashboard ### Administrative Operations The **Azure Virtual Machine - Administrative Operations** dashboard provides details on the operational activities and status of your Azure Virtual Machine resources. Use this dashboard to: * Monitor the distribution of operation types and their success rates to ensure proper functioning of your Virtual Machine. * Identify potential issues by analyzing the top operations causing errors and correlating them with specific users or applications. * Track recent write and delete operations to maintain an audit trail of changes made to your Virtual Machine. Azure Virtual Machine - Administrative Operations dashboard ### Policy and Recommendations The **Azure Virtual Machine - Policy and Recommendations** dashboard provides details on policy events and recommendations for your Azure Virtual Machine resources. Use this dashboard to: * Monitor the success and failure rates of policy events to ensure proper configuration and compliance. * Track and analyse recent recommendations to improve the performance and security of your VM setup. * Identify trends in policy events and recommendations over time to proactively address potential issues. Azure Virtual Machine - Policy and Recommendations dashboard ### CPU The **Azure Virtual Machine - CPU** dashboard provides details on the CPU metrics and usage of your Azure VM CPU. Azure Virtual Machine - CPU dashboard ### Cache The **Azure Virtual Machine - Cache** dashboard provides details on the status and usage of your Azure VM cache resources. Azure Virtual Machine - Cache dashboard ### Temp Disk The **Azure Virtual Machine - Temp Disk** dashboard provides details on the operational activities and status of your Azure VM Temp Disk. Azure Virtual Machine - Temp Disk dashboard ## Create monitors for Azure Virtual Machine app import CreateMonitors from '../../reuse/apps/create-monitors.md'; ### Azure Virtual Machine alerts These alerts are metric based and will work for all Virtual Machine. | Alert Name | Description | Alert Condition | Recover Condition | |:--|:--|:--|:--| | `Azure Virtual Machine - Available Memory Monitor` | This alert is triggered when memory drop under 1GB are detected for any VM.| Count < 1 | Count >= 1 | | `Azure Virtual Machine - CPU Usage Percentage Monitor` | This alert is triggered when CPU usage spikes above 80% are detected for any VM. | Count >= 80 | Count < 80 | | `Azure Virtual Machine - Availability Monitor` | This alert is triggered when VM Availability drops under 100% are detected for any VM. | Count < 1 | Count = 1 | | `Azure Virtual Machine - Data Disk IOPs Consumed Monitor` | This alert is triggered when Data Disk IOPs consumption percentage spikes above 95% are detected for any VM. | Count > 95 | Count =< 95 | | `Azure Virtual Machine - OS Disk IOPs Consumed Monitor`| This alert is triggered when OS Disk IOPs consumption percentage spikes above 95% are detected for any VM. | Count > 95 | Count =< 95 | ## Upgrade/Downgrade the Azure Virtual Machine app (optional) import AppUpdate from '../../reuse/apps/app-update.md'; ## Uninstalling the Azure Virtual Machine app (optional) import AppUninstall from '../../reuse/apps/app-uninstall.md'; ## Troubleshooting ### Metrics collection via Azure Metrics Source To troubleshoot metrics collection via Azure Metrics Source, follow the instructions in [Troubleshooting Azure Metrics Source](/docs/send-data/hosted-collectors/microsoft-source/azure-metrics-source/#troubleshooting). ### App installation failed - Content install error - Rule with name AzureObservabilityMetadataExtractionVMName already exists. This error occurs if the app being installed attempts to create a Metric Rule by a name (AzureObservabilityMetadataExtractionVMName) which already exists in the org. This Metric Rule could have been created manually and is creating conflict with current app installation flow. To resolve the issue, delete the existing Metric Rule (AzureObservabilityMetadataExtractionVMName) and reinstall the app.