Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: Function Support for Canvas App Instrumentation Key #703

Open
improving-jeffd opened this issue Jul 18, 2024 · 0 comments
Open

Comments

@improving-jeffd
Copy link

improving-jeffd commented Jul 18, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant