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
+106Lines changed: 106 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,8 @@ The below instructions applies to App Service Environment v3.
16
16
17
17
For Azure App Service Environment, you can collect the following logs:
18
18
19
+
-**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).
20
+
19
21
***App Service Environment Platform Logs**. Logs are only emitted when your App Service Environment has an event (for example, a scale operation with an App Service plan) that triggers the logs. To learn more about the different situations and messages collected for Azure App Service Environment, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/app-service/environment/using#logging).
20
22
21
23
## Setup
@@ -28,8 +30,52 @@ You must explicitly enable diagnostic settings for each Azure App Service Enviro
28
30
29
31
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
32
33
+
### Configure Field Extraction Rules
34
+
35
+
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.
In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.
34
80
35
81
1. To set up the Azure Event Hubs source in Sumo Logic, refer to [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
@@ -38,3 +84,63 @@ In this section, you will configure a pipeline for shipping diagnostic logs from
38
84
* Select `App Service Environment Platform Logs`.
39
85
* 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.
40
86
87
+
#### Activity logs (optional)
88
+
89
+
To collect activity logs, follow the instructions [here](/docs/integrations/microsoft-azure/audit). If you are already collecting activity logs for a subscription, do not perform this step.
90
+
91
+
## Installing the Azure App Service Environment app
92
+
93
+
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.
94
+
95
+
import AppInstall2 from '../../reuse/apps/app-install-v2.md';
96
+
97
+
<AppInstall2/>
98
+
99
+
## Viewing Azure App Service Environment dashboards
100
+
101
+
import ViewDashboards from '../../reuse/apps/view-dashboards.md';
102
+
103
+
<ViewDashboards/>
104
+
105
+
### Overview
106
+
107
+
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.
108
+
109
+
Use this dashboard to:
110
+
* View recent resource and service health incidents.
111
+
* View distribution of service and resource health by incident type.
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.
128
+
129
+
Use this dashboard to:
130
+
* Identify top users performing administrative operations.
131
+
* View Top 10 operations that caused the most errors.
0 commit comments