chore(tracing): deprecate tracer.configure params #14954
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.
Description
Improves tracer configuration performance and API consistency by deprecating specific
tracer.configure()
parameters.Changes:
trace_processors
→ usetracer.processors
(no longer resets SpanAggregator)context_provider
→ usetracer.context_provider
(removes duplicate API)apm_tracing_disabled
→ useapm_tracing_enabled
(consistent naming with other parameters)Testing
Updated tests and added deprecation warnings for 4.0.0 removal.
Risks
Low - backward compatibility maintained for 3.x
Additional Notes
Reduces processor update overhead and reduces the size of the configuration API.