Adaptive Runtime Application Insights needs to use Connection String instead of Instrumentation Key #5455
Labels
Area: Runtime
Adaptive Runtime
feature-request
A request for new functionality or an enhancement to an existing one.
needs-triage
The issue has just been created and it has not been reviewed by the team.
We have a customer who were experiencing some dropped events from their bot runtime to Application Insights. After investigation and the MS account team engaging with the App Insights, apparently this can happen if you are using the InstrumentationKey and not the Connection String, which the bot runtime currently does.
The new Adaptive Runtime should be updated to use the Connection String and, in fact, it looks like this is required for new Azure regions https://docs.microsoft.com/en-us/azure/azure-monitor/app/asp-net-troubleshoot-no-data
We will need to consider what, if anything we can do for legacy runtime, or what we do if we migrate a runtime that currently has an InstrumentationKey.
We should make this change now before we GA the runtime.
The text was updated successfully, but these errors were encountered: