change app insights example from key to connection string

daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-appinsights.md

@@ -11,15 +11,15 @@ Dapr integrates with [OpenTelemetry (OTEL) Collector](https://github.com/open-te
 ## Prerequisites
 
 - [Install Dapr on Kubernetes]({{< ref kubernetes >}})
-- [Set up an App Insights resource](https://docs.microsoft.com/azure/azure-monitor/app/create-new-resource) and make note of your App Insights instrumentation key.
+- [Set up an App Insights resource](https://docs.microsoft.com/azure/azure-monitor/app/create-new-resource) and make note of your App Insights connection string.
 
 ## Set up OTEL Collector to push to your App Insights instance
 
 To push events to your App Insights instance, install the OTEL Collector to your Kubernetes cluster.
 
 1. Check out the [`open-telemetry-collector-appinsights.yaml`](/docs/open-telemetry-collector/open-telemetry-collector-appinsights.yaml) file. 
 
-1. Replace the `<INSTRUMENTATION-KEY>` placeholder with your App Insights instrumentation key.
+1. Replace the `<CONNECTION_STRING>` placeholder with your App Insights connection string.
 
 1. Apply the configuration with: 
 

daprdocs/static/docs/open-telemetry-collector/open-telemetry-collector-appinsights.yaml

@@ -20,8 +20,7 @@ data:
       debug:
         verbosity: basic
       azuremonitor:
-        endpoint: "https://dc.services.visualstudio.com/v2/track"
-        instrumentation_key: "<INSTRUMENTATION-KEY>"
+        connection_string: "<CONNECTION_STRING>"
         # maxbatchsize is the maximum number of items that can be
         # queued before calling to the configured endpoint
         maxbatchsize: 100