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

Fix possible NoSuchBeanDefinitionException in Spring Monitor #37870

Merged

Conversation

jeanbisutti
Copy link
Contributor

Workaround waiting for the release of this OTel fix.

@github-actions github-actions bot added the azure-spring All azure-spring related issues label Nov 30, 2023
@azure-sdk
Copy link
Collaborator

API change check

APIView has identified API level changes in this PR and created following API reviews.

spring-cloud-azure-starter-monitor

Comment on lines +1 to +2
spring.datasource.url=jdbc:otel:h2:mem:db
spring.datasource.driver-class-name=io.opentelemetry.instrumentation.jdbc.OpenTelemetryDriver
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a question unrelated to this PR, why is :otel: needed in the url if the driver-class-name is already specifically using OpenTelemetryDriver?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a question unrelated to this PR, why is :otel: needed in the url if the driver-class-name is already specifically using OpenTelemetryDriver?

Need to check the implementation. Today the datasource url has to start with jdbc:otel:.

@jeanbisutti jeanbisutti merged commit f0a4d3d into main Nov 30, 2023
36 checks passed
@jeanbisutti jeanbisutti deleted the fix-possible-no-such-bean-exception-in-spring-monitor branch November 30, 2023 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
azure-spring All azure-spring related issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants