You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/integrations/microsoft-azure/azure-app-service-environment.md
+18-61Lines changed: 18 additions & 61 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ An [Azure App Service Environment](https://learn.microsoft.com/en-us/azure/app-s
12
12
13
13
The below instructions applies to App Service Environment v3.
14
14
15
-
## Log and metric types
15
+
## Log types
16
16
17
17
For Azure App Service Environment, you can collect the following logs:
18
18
@@ -26,62 +26,7 @@ Azure service sends monitoring data to Azure Monitor, which can then [stream dat
26
26
27
27
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).
28
28
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.
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`.
85
30
86
31
### Configure logs collection
87
32
@@ -105,15 +50,27 @@ To collect activity logs, follow the instructions [here](/docs/integrations/micr
105
50
106
51
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.
107
52
108
-
import AppInstall2 from '../../reuse/apps/app-install-v2.md';
53
+
import AppInstallIndexV2 from '../../reuse/apps/app-install-index-option.md';
109
54
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).
111
68
112
69
## Viewing Azure App Service Environment dashboards
113
70
114
-
import ViewDashboards from '../../reuse/apps/view-dashboards.md';
71
+
import ViewDashboardsIndex from '../../reuse/apps/view-dashboards-index.md';
0 commit comments