Azure App Service Plan

Azure App Service Plan 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.
Platform Metrics for Azure App Service Plan. These metrics are available in the Microsoft.Web/serverfarms namespace. For more information on supported metrics, refer to the Azure documentation. 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. Sumo Logic supports:

Logs collection from Azure Monitor using our Azure Event Hubs source.
Metrics collection using our 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.

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 metrics collection

To set up the Azure Metrics source in Sumo Logic, refer to Azure Metrics Source.

Configure logs collection

Diagnostic logs

In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.

To set up the Azure Event Hubs source in Sumo Logic, refer to Azure Event Hubs Source for Logs.
To create the Diagnostic setting in the Azure portal, refer to the Azure documentation. Perform the steps below for each Azure Functions that you want to monitor.
1. Choose Stream to an event hub as the destination.
2. Select AllMetrics.
3. Use the Event Hub namespace and Event Hub name configured in previous step in destination details section. You can use the default policy RootManageSharedAccessKey as the policy name.
Tag the location field in the source with right location value.

Activity logs (optional)

To collect activity logs, follow the instructions here. If you are already collecting activity logs for a subscription, do not perform this step.

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.

To install the app, do the following:

note

Next-Gen App: To install or update the app, you must be an account administrator or a user with Manage Apps, Manage Monitors, Manage Fields, Manage Metric Rules, and Manage Collectors capabilities depending upon the different content types part of the app.

Select App Catalog.
In the 🔎 Search Apps field, run a search for your desired app, then select it.
Click Install App.
note
Sometimes this button says Add Integration.
Click Next in the Setup Data section.
In the Configure App section of your respective app, complete the following field.
1. Index. Specify value for _index if the collection is configured with custom partition. Learn more. Default value is set to sumologic_default (default partition)
Click Next. You will be redirected to the Preview & Done section.

Post-installation

Once your app is installed, it will appear in your Installed Apps folder, and dashboard panels will start to fill automatically.

Each panel slowly fills with data matching the time range query received since the panel was created. Results will not immediately be available but will be updated with full graphs and charts over time.

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.
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

All dashboards have a set of filters that you can apply to the entire dashboard. Use these filters to drill down and examine the data to a granular level.

You can change the time range for a dashboard or panel by selecting a predefined interval from a drop-down list, choosing a recently used time range, or specifying custom dates and times. Learn more.
You can use template variables to drill down and examine the data on a granular level. For more information, see Filtering Dashboards with Template Variables.
Many of the Next-Gen apps allow you to provide the Index at the installation time and a default value for this key (sumologic_default). Based on your input, the app dashboards will be parameterized with a dashboard variable, allowing you to change the data partition queried by all panels. This restricts the query scope of all the dashboard queries to a specific data partition.

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.

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.

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

From your App Catalog:

From the Sumo Logic navigation, select App Catalog.
In the Search Apps field, search for and then select your app.
Make sure the app is installed.
Navigate to What's Included tab and scroll down to the Monitors section.
Click Create next to the pre-configured monitors. In the create monitors window, adjust the trigger conditions and notifications settings based on your requirements.
Scroll down to Monitor Details.
Under Location click on New Folder.
note
By default, monitor will be saved in the root folder. So to make the maintenance easier, create a new folder in the location of your choice.
Enter Folder Name. Folder Description is optional.
tip
Using app version in the folder name will be helpful to determine the versioning for future updates.
Click Create. Once the folder is created, click on Save.