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

APPLICATIONINSIGHTS_CONFIGURATION_CONTENT will not be considered in Azure Functions #3761

Open
franden opened this issue Jul 1, 2024 · 0 comments
Assignees

Comments

@franden
Copy link

franden commented Jul 1, 2024

Expected behavior

Content of environment variable APPLICATIONINSIGHTS_CONFIGURATION_CONTENT is considered by application insights agent

Actual behavior

We are using a quarkus framework to create and run our Azure Function. We set the application insights setting "Collection level" to Recommended so that the application insights agent is automatically added. Because vertx communication is not visible in the Application Insights we would like to enable it via entry in applicationinsights.json

{
   "preview":{
      "instrumentation":{
         "vertx":{
            "enabled":true
         }
      }
   }
}

we provided the content via environment variable APPLICATIONINSIGHTS_CONFIGURATION_CONTENT, but the issue is still present. We added some more configuration to APPLICATIONINSIGHTS_CONFIGURATION_CONTENT, but it seems that this doesn't have any effect. Even if the content is not a valid json, nothing happens (even no logs).

To Reproduce

  1. create quarkus application
  2. deploy the application
  3. set the "Collection level" to Recommended
  4. set environment variable APPLICATIONINSIGHTS_CONFIGURATION_CONTENT with some content

System information

Please provide the following information:

  • Quarkus 3.11.1 it uses azure-functions-java-library 3.1.0
  • Java 17
  • Azure Function OS: Linux
  • Azure Function Runtime version: 4.34.2.2
  • Used application insights agent version: ?? is not printed in the log

Logs

Screenshots

@heyams heyams self-assigned this Jul 3, 2024
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

2 participants