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/api-center/enable-api-analysis-linting.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ The following diagram shows the steps to enable linting and analysis in your API
53
53
* The Event Grid resource provider registered in your subscription. If you need to register the Event Grid resource provider, see [Subscribe to events published by a partner with Azure Event Grid](../event-grid/subscribe-to-partner-events.md#register-the-event-grid-resource-provider).
> `az apic` commands require the `apic-extension` Azure CLI extension. If you haven't used `az apic` commands, the extension is installed dynamically when you run your first `az apic` command. Learn more about [Azure CLI extensions](/cli/azure/azure-cli-extensions-overview).
Copy file name to clipboardExpand all lines: articles/api-management/migrate-stv1-to-stv2-no-vnet.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ API Management platform migration from `stv1` to `stv2` involves updating the un
41
41
42
42
* An API Management instance hosted on the `stv1` compute platform. To confirm that your instance is hosted on the `stv1` platform, see [How do I know which platform hosts my API Management instance?](compute-infrastructure.md#how-do-i-know-which-platform-hosts-my-api-management-instance)
See [Monitor Azure Functions](monitor-functions.md) for details on the data you can collect for Azure Functions and how to use it.
16
16
17
17
See [Monitor executions in Azure Functions](functions-monitoring.md) for details on using Application Insights to collect and analyze log data from individual functions in your function app.
There are two metrics specific to Functions that are of interest:
22
22
@@ -30,14 +30,14 @@ These metrics are used specifically when [estimating Consumption plan costs](fun
30
30
### Supported metrics for Microsoft.Web/sites
31
31
The following table lists the metrics available for the Microsoft.Web/sites resource type. Most of these metrics apply to both FunctionApps and WebApps.
Azure Functions integrates with Azure Monitor Logs to monitor functions. For detailed instructions on how to set up diagnostic settings to configure and route resource logs, see [Create diagnostic settings in Azure Monitor](/azure/azure-monitor/platform/diagnostic-settings).
37
37
38
38
:::image type="content" source="media/monitor-functions/choose-table.png" alt-text="Screenshot of adding a diagnostic setting for Azure Functions.":::
39
39
40
40
For the available resource log categories, their associated Log Analytics tables, and the logs schemas for Azure Functions, see [Azure Functions monitoring data reference](monitor-functions-reference.md#resource-logs).
Azure Functions also offers the ability to collect more than Azure Monitor resource logs. To view a near real time stream of application log files generated by your function running in Azure, you can connect to Application Insights and use Live Metrics Stream. Or, you can use the App Service platform built-in log streaming to view a stream of application log files. For more information, see [Enable streaming execution logs in Azure Functions](streaming-logs.md).
@@ -61,7 +61,7 @@ Azure Functions writes all logs to the **FunctionAppLogs** table under **LogMana
61
61
62
62
:::image type="content" source="media/monitor-functions/querying.png" alt-text="Screenshot of the Query window for Azure Functions in a Log Analytics workspace.":::
The following table lists common and recommended alert rules for Azure Functions. These are just recommended alerts. You can set alerts for any metric, log entry, or activity log entry listed in the [Monitoring data reference for Azure Functions](monitor-functions-reference.md).
@@ -123,7 +123,7 @@ The following table lists common and recommended alert rules for Azure Functions
123
123
| Activity Log | Restart function app| When app is restarted|
124
124
| Activity Log | Stop function app| When app is stopped|
For a list of all Azure Monitor supported metrics, including Azure Cosmos DB, see [Azure Monitor supported metrics](/azure/azure-monitor/essentials/metrics-supported).
20
20
21
21
### Supported metrics for Microsoft.DocumentDB/DatabaseAccounts
22
22
The following table lists the metrics available for the Microsoft.DocumentDB/DatabaseAccounts resource type.
@@ -192,7 +192,7 @@ The following table lists properties of resource logs in Azure Cosmos DB. The re
192
192
|**resourceTokenUserRid**|**resourceTokenUserRid_s**| This value is non-empty when [resource tokens](./secure-access-to-data.md#resource-tokens) are used for authentication. The value points to the resource ID of the user. |
193
193
|**responseLength**|**responseLength_s**| The length of the response, in bytes.|
0 commit comments