--- id: azure-app-service-plan title: Azure App Service Plan description: Learn about the Sumo Logic collection process for the Azure App Service Plan service. slug: /help/docs/integrations/microsoft-azure/azure-app-service-plan/ canonical: https://www.sumologic.com/help/docs/integrations/microsoft-azure/azure-app-service-plan/ --- import useBaseUrl from '@docusaurus/useBaseUrl'; Azure App Service Plan icon [Azure App Service Plan](https://learn.microsoft.com/en-us/azure/app-service/overview-hosting-plans) defines a set of compute resources for a app service to run. This integration helps in monitoring memory, CPU, incoming and outgoing bandwidth, number of sockets and their states across all the instances of the plan. ## Log and metric types For Azure App Service Plan, you can collect the following metrics: - **Activity logs**, provides insight into any subscription-level or management group level events that have occurred in the Azure. To learn more, refer to [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/activity-log-schema). - **Platform Metrics for Azure App Service Plan**. These metrics are available in the [Microsoft.Web/serverfarms](https://learn.microsoft.com/en-us/azure/azure-monitor/reference/supported-metrics/microsoft-web-serverfarms-metrics) namespace. For more information on supported metrics, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/app-service/web-sites-monitor#understand-metrics). App Service Plan metrics are available only for plans in Basic, Standard, Premium and Isolated tiers. ## 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/hosted-collectors/cloud-to-cloud-integration-framework/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 Azure App Service plan 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/AppServicePlan/Logs`, `Azure/AppServicePlan/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 ### Configure metrics collection import MetricsSource from '../../reuse/metrics-source.md'; #### Activity logs (optional) import ActivityLogs from '../../reuse/apps/azure-activity-logs.md'; ## Installing the Azure App Service Plan app This section provides instructions on how to install the Azure App Service Plan app, and shows examples of each of the preconfigured dashboards you can use to analyze your data. 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 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 an Azure resource. - `service_name`. Services that can be accessed with an Azure resource (for example, in Azure Container Instances the service is Subscriptions). ## Viewing Azure App Service Plan dashboards import ViewDashboardsIndex from '../../reuse/apps/view-dashboards-index.md'; ### Overview The **Azure AppService - Overview** dashboard provides comprehensive information of all the service health incidents or resource health events associated with Azure AppService in your azure account. Use this dashboard to: * View recent resource and service health incidents. * View distribution of service and resource health by incident type. Azure AppService Overview dashboard ### Network The **Azure AppService - Network** dashboard offers comprehensive insights into the network performance and traffic for your Azure AppService. Use this dashboard to: * Analyze network traffic patterns and performance metrics. * Identify potential network issues affecting your applications. Azure AppService Network dashboard ### Resource Utilisation The **Azure AppService - Resource Utilisation** dashboard provides a comprehensive view of the resource utilisation metrics and activities associated with your Azure AppService. Use this dashboard to: * Monitor resource utilisation events and their impact on service availability. * Analyze trends in operational performance over time. Azure AppService Resource Utilisation dashboard ### Administrative Operations The **Azure AppService - Administrative Operations** dashboard provides details on read/write/delete specific changes, different operations used, top 10 operations that caused most errors, and users performing admin operations. Use this dashboard to: * Identify top users performing administrative operations. * View Top 10 operations that caused the most errors. * View recent read, write, and delete operations. Azure AppService Administrative Operations dashboard ## Create monitors for Azure App Service Plan import CreateMonitors from '../../reuse/apps/create-monitors.md'; ### Azure App Service Plan alerts These alerts are metrics-based and will work for all app service plans. | Alert Name | Description | Alert Condition | Recover Condition | |:-|:-|:-|:-| | `Azure App Service Plan - CPU Usage` | This alert gets triggered when high CPU usage is detected in Azure App Service Plans. | Count > 90 | Count =< 90 | | `Azure App Service Plan - Disk Queue Length` | This alert gets triggered when Disk Queue Length becomes high and crosses the thresholds. Also, a warning type alert will be triggered when Disk Queue Length is greater than 2. | Count >= 4 | Count < 4 | | `Azure App Service Plan - HTTP Queue Length` | This alert gets triggered when the HTTP Queue Length is high and crosses the threshold. Also, a warning type alert will be triggered when HTTP Queue Length is greater than 80. | Count >= 100 | Count < 100 | | `Azure App Service Plan - Memory Usage` | This alert gets triggered when high Memory usage is detected in Azure App Service Plans. | Count > 80 | Count =< 80 | ## Upgrading the Azure App Service Plan app (Optional) import AppUpdate from '../../reuse/apps/app-update.md'; ## Uninstalling the Azure App Service Plan 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).