Fix #48576: Clarify tracing dependency requirements #48578
Closed
+6
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #48576
This pull request updates the Spring Boot documentation for Micrometer Tracing to clarify the modular tracing support introduced in Spring Boot 4.
Changes include:
Emphasizing that having spring-boot-starter-actuator on the classpath alone does not enable tracing.
Explaining that tracing is fully auto-configured only when a supported tracing bridge and tracer implementation (e.g., OpenTelemetry bridge + Zipkin) are present.
Updating the "Getting Started" and "Tracer Implementations" sections to reflect this requirement, so developers understand which dependencies are needed to enable tracing.
This ensures that users following the documentation will correctly configure tracing without confusion.