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/azure-functions/functions-monitoring.md
+23-23Lines changed: 23 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,29 +21,6 @@ You can try out Application Insights integration with Function Apps for free. Th
21
21
22
22
The full list of Application Insights features available to your function app is detailed in [Application Insights for Azure Functions supported features](../azure-monitor/app/azure-functions-supported-features.md).
23
23
24
-
## Enable Application Insights integration
25
-
26
-
For a function app to send data to Application Insights, it needs to know the instrumentation key of an Application Insights resource. The key must be in an app setting named **APPINSIGHTS_INSTRUMENTATIONKEY**.
27
-
28
-
When you create your function app [in the Azure portal](functions-create-first-azure-function.md), from the command line by using [Azure Functions Core Tools](functions-create-first-azure-function-azure-cli.md), or by using [Visual Studio Code](functions-create-first-function-vs-code.md), Application Insights integration is enabled by default. The Application Insights resource has the same name as your function app, and it's created either in the same region or in the nearest region.
29
-
30
-
### New function app in the portal
31
-
32
-
To review the Application Insights resource being created, select it to expand the **Application Insights** window. You can change the **New resource name** or choose a different **Location** in an [Azure geography](https://azure.microsoft.com/global-infrastructure/geographies/) where you want to store your data.
33
-
34
-

35
-
36
-
When you choose **Create**, an Application Insights resource is created with your function app, which has the `APPINSIGHTS_INSTRUMENTATIONKEY` set in application settings. Everything is ready to go.
When you create a function app using [Visual Studio](functions-create-your-first-function-visual-studio.md), you must create the Application Insights resource. You can then add the instrumentation key from that resource as an application setting in your function app.
Early versions of Functions used built-in monitoring, which is no longer recommended. When enabling Application Insights integration for such a function app, you must also [disable built-in logging](#disable-built-in-logging).
46
-
47
24
## View telemetry in Monitor tab
48
25
49
26
With [Application Insights integration enabled](#enable-application-insights-integration), you can view telemetry data in the **Monitor** tab.
@@ -565,6 +542,29 @@ You can write custom code to show the dependencies. For examples, see the sample
Whenyoucreateyourfunctionapp [intheAzureportal](functions-create-first-azure-function.md), fromthecommandlinebyusing [AzureFunctionsCoreTools](functions-create-first-azure-function-azure-cli.md), orbyusing [VisualStudioCode](functions-create-first-function-vs-code.md), ApplicationInsightsintegrationisenabledbydefault. TheApplicationInsightsresourcehasthesamenameasyourfunctionapp, andit's created either in the same region or in the nearest region.
550
+
551
+
### New function app in the portal
552
+
553
+
ToreviewtheApplicationInsightsresourcebeingcreated, selectittoexpandthe**ApplicationInsights**window. Youcanchangethe**Newresourcename**orchooseadifferent**Location**inan [Azuregeography](https://azure.microsoft.com/global-infrastructure/geographies/) where you want to store your data.
0 commit comments