Merge pull request #218640 from ggailey777/insights

Port App Insights content to Functions

Author: v-ccolin

.openpublishing.redirection.json

@@ -7018,6 +7018,11 @@
             "redirect_url": "/azure/azure-functions/functions-event-grid-blob-trigger",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/azure-monitor/app/azure-functions-supported-features.md",
+            "redirect_url": "/azure/azure-functions/functions-monitoring",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/azure-government/documentation-government-k8.md",
             "redirect_url": "/azure/azure-government",

articles/azure-functions/configure-monitoring.md

@@ -195,7 +195,7 @@ You can exclude certain types of telemetry from sampling. In this example, data
 ```
 ---
 
-For more information, see [Sampling in Application Insights](../azure-monitor/app/sampling.md).
+If your project takes a dependency on the Application Insights SDK to do manual telemetry tracking, you may experience strange behavior if your sampling configuration differs from the sampling configuration in your function app. In such cases, use the same sampling configuration as the function app. For more information, see [Sampling in Application Insights](../azure-monitor/app/sampling.md).
 
 ## Enable SQL query collection
 

articles/azure-functions/functions-monitoring.md

@@ -36,6 +36,36 @@ Typically, you create an Application Insights instance when you create your func
 > [!IMPORTANT]
 > Sovereign clouds, such as Azure Government, require the use of the Application Insights connection string (`APPLICATIONINSIGHTS_CONNECTION_STRING`) instead of the instrumentation key. To learn more, see the [APPLICATIONINSIGHTS_CONNECTION_STRING reference](functions-app-settings.md#applicationinsights_connection_string).
 
+The following table details the supported features of Application Insights available for monitoring your function apps:
+
+| Azure Functions runtime version   | 1.x     | 2.x+ | 
+|-----------------------------------|:---------------:|:------------------:|
+| | | | 
+| **Automatic  collection of**        |               |                  |
+| • Requests                     | ✓           | ✓              |
+| • Exceptions                   | ✓           | ✓              |
+| • Performance Counters         | ✓           | ✓              |
+| • Dependencies                 |               |                  |
+|    — HTTP      |               | ✓              |
+|    — Service Bus|               | ✓              |
+|    — Event Hubs  |               | ✓              |
+|    — SQL\*       |               | ✓              |
+| | | | 
+| **Supported features**              |               |                  |
+| • QuickPulse/LiveMetrics       | Yes           | Yes              | 
+|    — Secure Control Channel |               | Yes | 
+| • Sampling                     | Yes           | Yes              | 
+| • Heartbeats                   | | Yes              | 
+| | | |
+| **Correlation**                    |               |                  |
+| • Service Bus                  |               | Yes              |
+| • Event Hubs                    |               | Yes              |
+| | | | 
+| **Configurable**                  |               |                  |           
+| •[Fully configurable](#custom-telemetry-data)           |               | Yes                 | 
+
+\* To enable the collection of SQL query string text, see [Enable SQL query collection](./configure-monitoring.md#enable-sql-query-collection).
+
 ## Collecting telemetry data
 
 With Application Insights integration enabled, telemetry data is sent to your connected Application Insights instance. This data includes logs generated by the Functions host, traces written from your functions code, and performance data. 
@@ -80,6 +110,10 @@ In addition to automatic dependency data collection, you can also use one of the
 + [Log custom telemetry in JavaScript functions](functions-reference-node.md#log-custom-telemetry) 
 + [Log custom telemetry in Python functions](functions-reference-python.md#log-custom-telemetry)
 
+### Performance Counters
+
+Automatic collection of Performance Counters isn't supported when running on Linux.
+
 ## Writing to logs 
 
 The way that you write to logs and the APIs you use depend on the language of your function app project.   

articles/azure-monitor/app/azure-functions-supported-features.md

@@ -1529,7 +1529,7 @@ items:
     - name: Endpoint overrides
       href: app/custom-endpoints.md
     - name: Azure Functions
-      href: app/azure-functions-supported-features.md
+      href: ../azure-functions/functions-monitoring.md
     - name: Statsbeat
       href: app/statsbeat.md
     - name: Release notes
@@ -1561,7 +1561,7 @@ items:
       - name: Context
         href: app/data-model-context.md
       - name: Integration with Azure Functions
-        href: app/azure-functions-supported-features.md
+        href: app/azure-functions-supported-features.md?toc=/azure/azure-monitor/toc.json
   - name: Azure PowerShell
     items:
     - name: Azure Monitor