Skip to content

Commit df095a6

Browse files
committed
Update azure-app-service-environment.md
1 parent 1bfb9b8 commit df095a6

File tree

1 file changed

+18
-61
lines changed

1 file changed

+18
-61
lines changed

docs/integrations/microsoft-azure/azure-app-service-environment.md

Lines changed: 18 additions & 61 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ An [Azure App Service Environment](https://learn.microsoft.com/en-us/azure/app-s
1212

1313
The below instructions applies to App Service Environment v3.
1414

15-
## Log and metric types
15+
## Log types
1616

1717
For Azure App Service Environment, you can collect the following logs:
1818

@@ -26,62 +26,7 @@ Azure service sends monitoring data to Azure Monitor, which can then [stream dat
2626

2727
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).
2828

29-
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`.
30-
31-
### Configure field in field schema
32-
33-
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Fields**. <br/>[**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**.
34-
1. Search for following fields:
35-
- `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).
36-
- `location`. The region to which the resource name belongs to.
37-
- `subscription_id`. ID associated with a subscription where resource is present.
38-
- `resource_group`. The resource group name where the Azure resource is present.
39-
- `provider_name`. Azure resource provider name (for example, Microsoft.WEB).
40-
- `resource_type`. Azure resource type (for example, SITES).
41-
- `resource_name`. The name of the resource (for example, Azure Function App name).
42-
1. Create the fields if they are not present. Refer to [Manage fields](/docs/manage/fields/#manage-fields).
43-
44-
### Configure Field Extraction Rules
45-
46-
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.
47-
48-
#### Azure location extraction FER
49-
50-
```sql
51-
Rule Name: AzureLocationExtractionFER
52-
Applied at: Ingest Time
53-
Scope (Specific Data): tenant_name=*
54-
```
55-
56-
```sql title="Parse Expression"
57-
json "location", "properties.resourceLocation", "properties.region" as location, resourceLocation, service_region nodrop
58-
| replace(toLowerCase(resourceLocation), " ", "") as resourceLocation
59-
| if (!isBlank(resourceLocation), resourceLocation, location) as location
60-
| if (!isBlank(service_region), service_region, location) as location
61-
| if (isBlank(location), "global", location) as location
62-
| fields location
63-
```
64-
65-
#### Resource ID extraction FER
66-
67-
```sql
68-
Rule Name: AzureResourceIdExtractionFER
69-
Applied at: Ingest Time
70-
Scope (Specific Data): tenant_name=*
71-
```
72-
73-
```sql title="Parse Expression"
74-
json "resourceId", "ResourceId" as resourceId1, resourceId2 nodrop
75-
| if (isBlank(resourceId1), resourceId2, resourceId1) as resourceId
76-
| toUpperCase(resourceId) as resourceId
77-
| parse regex field=resourceId "/SUBSCRIPTIONS/(?<subscription_id>[^/]+)" nodrop
78-
| parse field=resourceId "/RESOURCEGROUPS/*/" as resource_group nodrop
79-
| parse regex field=resourceId "/PROVIDERS/(?<provider_name>[^/]+)" nodrop
80-
| parse regex field=resourceId "/PROVIDERS/[^/]+(?:/LOCATIONS/[^/]+)?/(?<resource_type>[^/]+)/(?<resource_name>.+)" nodrop
81-
| parse regex field=resource_name "(?<parent_resource_name>[^/]+)(?:/PROVIDERS/[^/]+)?/(?<service_type>[^/]+)/?(?<service_name>.+)" nodrop
82-
| if (isBlank(parent_resource_name), resource_name, parent_resource_name) as resource_name
83-
| fields subscription_id, location, provider_name, resource_group, resource_type, resource_name, service_type, service_name
84-
```
29+
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`.
8530

8631
### Configure logs collection
8732

@@ -105,15 +50,27 @@ To collect activity logs, follow the instructions [here](/docs/integrations/micr
10550

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

108-
import AppInstall2 from '../../reuse/apps/app-install-v2.md';
53+
import AppInstallIndexV2 from '../../reuse/apps/app-install-index-option.md';
10954

110-
<AppInstall2/>
55+
<AppInstallIndexV2/>
56+
57+
As part of the app installation process, the following fields will be created by default:
58+
59+
- `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).
60+
- `location`. The region to which the resource name belongs to.
61+
- `subscription_id`. ID associated with a subscription where the resource is present.
62+
- `resource_group`. The resource group name where the Azure resource is present.
63+
- `provider_name`. Azure resource provider name (for example, Microsoft.Network).
64+
- `resource_type`. Azure resource type (for example, storage accounts).
65+
- `resource_name`. The name of the resource (for example, storage account name).
66+
- `service_type`. Type of the service that can be accessed with a Azure resource.
67+
- `service_name`. Services that can be accessed with an Azure resource (for example, in Azure Container Instances the service is Subscriptions).
11168

11269
## Viewing Azure App Service Environment dashboards
11370

114-
import ViewDashboards from '../../reuse/apps/view-dashboards.md';
71+
import ViewDashboardsIndex from '../../reuse/apps/view-dashboards-index.md';
11572

116-
<ViewDashboards/>
73+
<ViewDashboardsIndex/>
11774

11875
### Overview
11976

0 commit comments

Comments
 (0)