Skip to content

Application insights agent will be part of the java worker #585

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

Closed
shreyas-gopalakrishna opened this issue Jun 16, 2022 · 1 comment · Fixed by #586 or #656
Closed

Application insights agent will be part of the java worker #585

shreyas-gopalakrishna opened this issue Jun 16, 2022 · 1 comment · Fixed by #586 or #656

Comments

@shreyas-gopalakrishna
Copy link
Member

shreyas-gopalakrishna commented Jun 16, 2022

[Draft Issue - This is not yet released]

  • Application insights agent will be part of the java worker and included in worker release
  • Java consumption, dedicated and Elastic premium apps
    • Use APPLICATIONINSIGHTS_ENABLE_AGENT = true/false to enable and disable application insights
  • Java consumption apps
    • Application insights agent will start with the java process by default
    • To disable the agent from starting with java worker process use appsetting languageWorkers:java:arguments = -DaiAgentOptOut
      Please not this will increase cold start times.
@purijatin
Copy link

Would the behavior remain the same when deployed via docker image?

Currently, the documentation isn't clear when it comes to the docker image. This is what we are currently doing: https://stackoverflow.com/questions/71085054/java-azure-application-insights-dynamic-tracing-not-working-with-docker-images/71085468#71085468

And it is painful.

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