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

Feature Request: Set dapr-instrumentation-key after environment is created #293

Open
markharrison opened this issue Jul 1, 2022 · 12 comments
Assignees
Labels
Dapr Related to Dapr in ACA enhancement New feature or request

Comments

@markharrison
Copy link

Is there anyway I can set the dapr-instrumentation-key for Application Insights after the container apps environment has been created ?

I don't seem able to do using AZ CLI

@markharrison markharrison added the enhancement New feature or request label Jul 1, 2022
@ghost ghost added the Needs: triage 🔍 Pending a first pass to read, tag, and assign label Jul 1, 2022
@kevingbb
Copy link

kevingbb commented Jul 6, 2022

You can set the key via ARM or Bicep. The best practice is to create the Log Analytics and App Insights resources ahead of time, then pass them in at ACA Environment creation time.

@markharrison
Copy link
Author

thank you
if ARM/BICEP can do this - be good if the AZ CLI was enhanced to support too

@kendallroden kendallroden removed the Needs: triage 🔍 Pending a first pass to read, tag, and assign label Nov 2, 2022
@kendallroden kendallroden self-assigned this Nov 2, 2022
@kendallroden kendallroden added the Dapr Related to Dapr in ACA label Nov 2, 2022
@davidjones-pc
Copy link

Hi @kevingbb - I have tried adding the daprAIInstrumentationKey to an existing container app environment using bicep and ARM but I am not sure if it is working. If I export the template of the environment from the portal, after I have deployed the bicep template, it does not include the daprAIInstrumentationKey in it. I have also tried using the cli to show the properties of the container app environment and it is not shown in there either. Is there a way in the portal or cli where I can see that the value for daprAIInstrumentationKey has been set correctly?

@kevingbb
Copy link

Looping in @dariagrigoriu and @torosent to comment on the above.

@torosent
Copy link
Member

Hi. It's currently not supported but we are working on it. ETA - End of March

@jsheetzmt
Copy link

Any updates on this? Also looking for a way to add dapr-instrumentation-key to an existing environment.

@balajivijayakumar1994
Copy link

hi Team,

Any update on this ? How to add dapr-instrumentation-key through Azure portal or Azure CLI.

If yes could you please give sample command

Thanks
Balaji

@jsheetzmt
Copy link

jsheetzmt commented Jun 9, 2023

This ticket has been open almost an entire year. We use terraform for IAC, and it doesn't have a way to set the instrumentation key during container app env creation. Only option for us is adding the instrumentation after creation.

Looking to add instrumentation to an existing environment, especially now that we are seeing random performance issues when chaining together dapr service invocations.

Related issue: #556

@mahs86
Copy link

mahs86 commented Nov 3, 2023

Everyone is eagerly waiting for the upcoming integration efforts here. Kindly expedite at the earliest.

@jpm1
Copy link

jpm1 commented Jan 17, 2024

I also fell into the trap and created my environment using Azure GUI and now I'm looking for a way to add this dapr instrumentation key to my existing environment!

Will it be possible to do this soon via the Azure GUI or the CLI. I don't want to use either ARM or Bicep which I don't know well.

@hernandoz
Copy link

Hi , as everyone else on this thread waiting for a way to update the instrumentation key for Dapr .

@VenkataRKC
Copy link

Any update on this of updating the
daprAIInstrumentationKey after the azure container environment is created .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dapr Related to Dapr in ACA enhancement New feature or request
Projects
None yet
Development

No branches or pull requests