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
Adding instrumentation key is a nice way to trace all the events in Azure AppInsights but hard-coding it defeats the purpose. When we deploy the App from DEV to QA or to PROD we would like to use different Instrumentation Key per environment.
Current work arounds are to manually edit the App in downstream environments, or Unpack -> string replace the key -> pack in your pipelines. That second approach feels somewhat hacky and breaks when you have complex Canvas Apps that use features not supported with Unpack/Pack (Haven't tried the latest PAC CLI Update that made some strides here, so I'll check that out).
In the meantime though, the idea is to make Instrumentation Key accept a function so we can set it dynamically. For example, by using Environment Variable which will store the instrumentation key which can also be part of ALM process.
Adding instrumentation key is a nice way to trace all the events in Azure AppInsights but hard-coding it defeats the purpose. When we deploy the App from DEV to QA or to PROD we would like to use different Instrumentation Key per environment.
Current work arounds are to manually edit the App in downstream environments, or Unpack -> string replace the key -> pack in your pipelines. That second approach feels somewhat hacky and breaks when you have complex Canvas Apps that use features not supported with Unpack/Pack (Haven't tried the latest PAC CLI Update that made some strides here, so I'll check that out).
In the meantime though, the idea is to make Instrumentation Key accept a function so we can set it dynamically. For example, by using Environment Variable which will store the instrumentation key which can also be part of ALM process.
Credit to Power Maverick from the following PowerApps Ideas post:
https://ideas.powerapps.com/d365community/idea/f04de441-4b7a-4e30-a681-4626a796d38a
The text was updated successfully, but these errors were encountered: