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

HTTP trace collection stopped after upgrade to App Insights 3.5.4 for application based on Spring Boot 3.3.1 #3839

Open
vap78 opened this issue Aug 14, 2024 · 4 comments
Assignees
Labels

Comments

@vap78
Copy link

vap78 commented Aug 14, 2024

Expected behavior

HTTP traces should be collected and reported to application insights

Actual behavior

They are not. Only Service bus calls, logs and metrics are recorded

To Reproduce

We have a Spring Boot 3.3.1 / Java 21 application using Azure Application Insights integration. The library runs in agent mode as described here: https://learn.microsoft.com/en-us/azure/azure-monitor/app/java-spring-boot

After the upgrade to version 3.5.4 of the agent, we no longer receive http access log entries into our App Insights instance. Logs and metrics keep coming.
Everything was working fine with the previous version we used: 3.4.2.
I see that there is a breaking change in regard to http trace collection in the release notes, but the link with the details is broken.

Additional configuration we have on this instance - following env variables are set:

  • APPLICATIONINSIGHTS_INSTRUMENTATION_LOGGING_LEVEL: "ALL"
  • APPLICATIONINSIGHTS_INSTRUMENTATION_REDIS_ENABLED: "false"
  • APPLICATIONINSIGHTS_INSTRUMENTATION_JDBC_ENABLED: "false"
  • APPLICATIONINSIGHTS_INSTRUMENTATION_RABBITMQ_ENABLED: "false"
  • APPLICATIONINSIGHTS_INSTRUMENTATION_MICROMETER_ENABLED: "false"

System information

Please provide the following information:

  • SDK Version: 3.5.4
  • OS type and version: K8S container based on Alpine Linux
  • Application Server type and version (if applicable): Spring Boot 3.3.1 running on Open JDK 21
  • Using spring-boot: yes
  • Additional relevant libraries (with version, if applicable):

Logs

I attach logs from a sample start of a test instance that received some http requests.

Screenshots

If applicable, add screenshots to help explain your problem.
out.txt

@heyams
Copy link
Contributor

heyams commented Aug 15, 2024

@vap78 can you please provide us a self-diagnostics log at the TRACE level? We want to confirm if tomcat 7 and jakarta servlet are both present in your application, which might cause some conflict in OpenTelemetry upstream.

APPLICATIONINSIGHTS_SELF_DIAGNOSTICS_LEVEL=TRACE

@vap78
Copy link
Author

vap78 commented Aug 16, 2024

Hi

attaching logs as requested.

Best regards
Vasil
logs.zip

@heyams
Copy link
Contributor

heyams commented Aug 16, 2024

@vap78 trace log confirmed that both jakarta and tomcat7 are present.
Upstream has a fix, release is coming out today or early next week. We'll integrate it in version 3.6.0, which is planned to be released next week or the week after next week if no blocker. Please watch for our new releases.

@vap78
Copy link
Author

vap78 commented Aug 16, 2024

Thank you very much for the quick reaction :)

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

No branches or pull requests

2 participants