From df095a6ebd77998b90cdd8aa44db8204f751c5e9 Mon Sep 17 00:00:00 2001 From: Amee Lepcha Date: Wed, 18 Jun 2025 18:29:28 +0530 Subject: [PATCH 1/3] Update azure-app-service-environment.md --- .../azure-app-service-environment.md | 79 +++++-------------- 1 file changed, 18 insertions(+), 61 deletions(-) diff --git a/docs/integrations/microsoft-azure/azure-app-service-environment.md b/docs/integrations/microsoft-azure/azure-app-service-environment.md index 4c56bd9c8a..8e71b64867 100644 --- a/docs/integrations/microsoft-azure/azure-app-service-environment.md +++ b/docs/integrations/microsoft-azure/azure-app-service-environment.md @@ -12,7 +12,7 @@ An [Azure App Service Environment](https://learn.microsoft.com/en-us/azure/app-s The below instructions applies to App Service Environment v3. -## Log and metric types +## Log types For Azure App Service Environment, you can collect the following logs: @@ -26,62 +26,7 @@ Azure service sends monitoring data to Azure Monitor, which can then [stream dat You must explicitly enable diagnostic settings for each Azure App Service Environment 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/AppServiceEnvironment/Logs`, `Azure/AppServiceEnvironment/Metrics`. - -### Configure field in field schema - -1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Fields**.
[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Fields**. You can also click the **Go To...** menu at the top of the screen and select **Fields**. -1. Search for following fields: - - `tenant_name`. This field is tagged at the collector level and 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 resource is present. - - `resource_group`. The resource group name where the Azure resource is present. - - `provider_name`. Azure resource provider name (for example, Microsoft.WEB). - - `resource_type`. Azure resource type (for example, SITES). - - `resource_name`. The name of the resource (for example, Azure Function App name). -1. Create the fields if they are not present. Refer to [Manage fields](/docs/manage/fields/#manage-fields). - -### Configure Field Extraction Rules - -Create a Field Extraction Rule (FER) by following the instructions [here](/docs/manage/field-extractions/create-field-extraction-rule/). If the FER already exists with same name, then skip this step. - -#### Azure location extraction FER - -```sql -Rule Name: AzureLocationExtractionFER -Applied at: Ingest Time -Scope (Specific Data): tenant_name=* -``` - -```sql title="Parse Expression" -json "location", "properties.resourceLocation", "properties.region" as location, resourceLocation, service_region nodrop -| replace(toLowerCase(resourceLocation), " ", "") as resourceLocation -| if (!isBlank(resourceLocation), resourceLocation, location) as location -| if (!isBlank(service_region), service_region, location) as location -| if (isBlank(location), "global", location) as location -| fields location -``` - -#### Resource ID extraction FER - -```sql -Rule Name: AzureResourceIdExtractionFER -Applied at: Ingest Time -Scope (Specific Data): tenant_name=* -``` - -```sql title="Parse Expression" -json "resourceId", "ResourceId" as resourceId1, resourceId2 nodrop -| if (isBlank(resourceId1), resourceId2, resourceId1) as resourceId -| toUpperCase(resourceId) as resourceId -| parse regex field=resourceId "/SUBSCRIPTIONS/(?[^/]+)" nodrop -| parse field=resourceId "/RESOURCEGROUPS/*/" as resource_group nodrop -| parse regex field=resourceId "/PROVIDERS/(?[^/]+)" nodrop -| parse regex field=resourceId "/PROVIDERS/[^/]+(?:/LOCATIONS/[^/]+)?/(?[^/]+)/(?.+)" nodrop -| parse regex field=resource_name "(?[^/]+)(?:/PROVIDERS/[^/]+)?/(?[^/]+)/?(?.+)" nodrop -| if (isBlank(parent_resource_name), resource_name, parent_resource_name) as resource_name -| fields subscription_id, location, provider_name, resource_group, resource_type, resource_name, service_type, service_name -``` +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/AppServiceEnvironment/Logs`. ### Configure logs collection @@ -105,15 +50,27 @@ To collect activity logs, follow the instructions [here](/docs/integrations/micr This section provides instructions on how to install the Azure App Service Environment app, and shows examples of each of the preconfigured dashboards you can use to analyze your data. -import AppInstall2 from '../../reuse/apps/app-install-v2.md'; +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 Azure App Service Environment dashboards -import ViewDashboards from '../../reuse/apps/view-dashboards.md'; +import ViewDashboardsIndex from '../../reuse/apps/view-dashboards-index.md'; - + ### Overview From 89348f8b49186b5204f4b8830912ab4fc80277b3 Mon Sep 17 00:00:00 2001 From: Chetan Choudhary Date: Fri, 20 Jun 2025 14:23:50 +0530 Subject: [PATCH 2/3] Update docs/integrations/microsoft-azure/azure-app-service-environment.md Co-authored-by: John Pipkin (Sumo Logic) --- .../microsoft-azure/azure-app-service-environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/microsoft-azure/azure-app-service-environment.md b/docs/integrations/microsoft-azure/azure-app-service-environment.md index 8e71b64867..71f18f22cd 100644 --- a/docs/integrations/microsoft-azure/azure-app-service-environment.md +++ b/docs/integrations/microsoft-azure/azure-app-service-environment.md @@ -57,7 +57,7 @@ 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. +- `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). From a1abbd4d7167a4e7d43cf2da1e71f72269b326f8 Mon Sep 17 00:00:00 2001 From: Chetan Choudhary Date: Fri, 20 Jun 2025 14:23:58 +0530 Subject: [PATCH 3/3] Update docs/integrations/microsoft-azure/azure-app-service-environment.md Co-authored-by: John Pipkin (Sumo Logic) --- .../microsoft-azure/azure-app-service-environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/microsoft-azure/azure-app-service-environment.md b/docs/integrations/microsoft-azure/azure-app-service-environment.md index 71f18f22cd..d165e5ed8d 100644 --- a/docs/integrations/microsoft-azure/azure-app-service-environment.md +++ b/docs/integrations/microsoft-azure/azure-app-service-environment.md @@ -63,7 +63,7 @@ As part of the app installation process, the following fields will be created by - `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_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 Environment dashboards