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: articles/app-service/monitor-app-service.md
+48-1Lines changed: 48 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,13 +15,28 @@ ms.service: app-service
15
15
16
16
## App Service monitoring
17
17
18
+
Azure App Service provides several monitoring options for monitoring resources for availability, performance, and operation. Options include Diagnostic Settings, Application Insights, log stream, metrics, quotas and alerts, and activity logs.
19
+
18
20
On the Azure portal page for your web app, you can select **Diagnose and solve problems** from the left navigation to access complete App Service diagnostics for your app. For more information about the App Service diagnostics tool, see [Azure App Service diagnostics overview](overview-diagnostics.md).
19
21
20
22
App Service provides built-in diagnostics logging to assist with debugging apps. For more information about the built-in logs, see [Stream diagnostics logs](troubleshoot-diagnostic-logs.md#stream-logs).
21
23
22
24
You can also use Azure Health check to monitor App Service instances. For more information, see [Monitor App Service instances using Health check](monitor-instances-health-check.md).
23
25
24
-
For a complete overview and summary of App Service monitoring options, see [Azure App Service monitoring overview](overview-monitoring.md).
26
+
If you're using ASP.NET Core, ASP.NET, Java, Node.js, or Python, we recommend [enabling observability with Application Insights](/azure/azure-monitor/app/opentelemetry-enable). To learn more about observability experiences offered by Application Insights, see [Application Insights overview](/azure/azure-monitor/app/app-insights-overview).
27
+
28
+
### Monitoring scenarios
29
+
30
+
The following table lists monitoring methods to use for different scenarios.
31
+
32
+
|Scenario|Monitoring method |
33
+
|----------|-----------|
34
+
|I want to monitor platform metrics and logs |[Azure Monitor platform metrics](#platform-metrics)|
35
+
|I want to monitor application performance and usage | (Azure Monitor) [Application Insights](#application-insights)|
36
+
|I want to monitor built-in logs for testing and development|[Log stream](troubleshoot-diagnostic-logs.md#stream-logs)|
37
+
|I want to monitor resource limits and configure alerts|[Quotas and alerts](web-sites-monitor.md)|
38
+
|I want to monitor web app resource events|[Activity logs](#activity-log)|
39
+
|I want to monitor metrics visually|[Metrics](web-sites-monitor.md#metrics-granularity-and-retention-policy)|
For a list of available metrics for App Service, see [App Service monitoring data reference](monitor-app-service-reference.md#metrics).
41
57
58
+
For help understanding metrics in App Service, see [Understand metrics](web-sites-monitor.md#understand-metrics). Metrics can be viewed by aggregates on data (ie. average, max, min, etc.), instances, time range, and other filters. Metrics can monitor performance, memory, CPU, and other attributes.
For the available resource log categories, their associated Log Analytics tables, and the logs schemas for App Service, see [App Service monitoring data reference](monitor-app-service-reference.md#resource-logs).
Azure activity logs for App Service include details such as:
71
+
72
+
- What operations were taken on the resources (ex: App Service Plans)
73
+
- Who started the operation
74
+
- When the operation occurred
75
+
- Status of the operation
76
+
- Property values to help you research the operation
77
+
78
+
Azure activity logs can be queried using the Azure portal, PowerShell, REST API, or CLI.
79
+
80
+
### Ship activity logs to Event Grid
81
+
82
+
While activity logs are user-based, there's a new [Azure Event Grid](../event-grid/index.yml) integration with App Service (preview) that logs both user actions and automated events. With Event Grid, you can configure a handler to react to the said events. For example, use Event Grid to instantly trigger a serverless function to run image analysis each time a new photo is added to a blob storage container.
83
+
84
+
Alternatively, you can use Event Grid with Logic Apps to process data anywhere, without writing code. Event Grid connects data sources and event handlers.
85
+
86
+
To view the properties and schema for App Service events, see [Azure App Service as an Event Grid source](../event-grid/event-schema-app-service.md).
87
+
88
+
## Log stream (via App Service Logs)
89
+
90
+
Azure provides built-in diagnostics to assist during testing and development to debug an App Service app. [Log stream](troubleshoot-diagnostic-logs.md#stream-logs) can be used to get quick access to output and errors written by your application, and logs from the web server. These are standard output/error logs in addition to web server logs.
Apps that are hosted in App Service are subject to certain limits on the resources they can use. [The limits](web-sites-monitor.md#understand-quotas) are defined by the App Service plan that's associated with the app. Metrics for an app or an App Service plan can be hooked up to alerts.
134
+
88
135
### App Service alert rules
89
136
90
137
The following table lists common and recommended alert rules for App Service.
Copy file name to clipboardExpand all lines: articles/app-service/troubleshoot-diagnostic-logs.md
+1-21Lines changed: 1 addition & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -197,27 +197,7 @@ With the new [Azure Monitor integration](https://aka.ms/appsvcblog-azmon), you c
197
197
198
198
### Supported log types
199
199
200
-
The following table shows the supported log types and descriptions:
201
-
202
-
| Log Name| Log type | Windows | Windows Container | Linux | Linux Container | Description |
203
-
|-|-|-|-|-|-|-|
204
-
| App Service Console Logs | AppServiceConsoleLogs | Java SE & Tomcat | Yes | Yes | Yes | Standard output and standard error <sup>3</sup> |
205
-
| HTTP logs | AppServiceHTTPLogs | Yes | Yes | Yes | Yes | Web server logs |
206
-
| App Service Environment Platform Logs | AppServiceEnvironmentPlatformLogs | Yes | N/A | Yes | Yes | App Service Environment: scaling, configuration changes, and status logs|
207
-
| Access Audit Logs | AppServiceAuditLogs | Yes | Yes | Yes | Yes | Login activity via FTP and Kudu |
208
-
| Site Content Change Audit Logs | AppServiceFileAuditLogs | Yes | Yes | TBA | TBA | File changes made to the site content; **only available for Premium tier and above** |
| Report Antivirus Audit Logs | AppServiceAntivirusScanAuditLogs <sup>4</sup> | Yes | Yes | Yes | Yes | [Anti-virus scan logs](https://azure.github.io/AppService/2020/12/09/AzMon-AppServiceAntivirusScanAuditLogs.html) using Microsoft Defender for Cloud; **only available for Premium tier** |
213
-
214
-
<sup>1</sup> For Tomcat apps, add `TOMCAT_USE_STARTUP_BAT` to the app settings and set it to `false` or `0`. Need to be on the *latest* Tomcat version and use *java.util.logging*.
215
-
216
-
<sup>2</sup> For Java SE apps, add `WEBSITE_AZMON_PREVIEW_ENABLED` to the app settings and set it to `true` or to `1`.
217
-
218
-
<sup>3</sup> Current logging limit is set to 100 logs per minute.
219
-
220
-
<sup>4</sup> AppServiceAntivirusScanAuditLogs log type is still currently in Preview
200
+
For a list of supported log types and their descriptions, see [Supported resource logs for Microsoft.Web](monitor-app-service-reference.md#supported-resource-logs-for-microsoftweb).
Diagnostic settings can be used to collect metrics for certain Azure services into Azure Monitor Logs for analysis with other monitoring data using log queries. For this tutorial, you enable the web server and standard output/error logs. See [supported log types](./troubleshoot-diagnostic-logs.md#supported-log-types) for a complete list of log types and descriptions.
72
+
Diagnostic settings can be used to collect metrics for certain Azure services into Azure Monitor Logs for analysis with other monitoring data using log queries. For this tutorial, you enable the web server and standard output/error logs. See [supported log types](monitor-app-service-reference.md#resource-logs) for a complete list of log types and descriptions.
73
73
74
74
You run the following commands to create diagnostic settings for AppServiceConsoleLogs (standard output/error) and AppServiceHTTPLogs (web server logs). Replace _\<app-name>_ and _\<workspace-name>_ with your values.
0 commit comments