You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(sampling): ensure agent based sampling is not reset after forking and on tracer.configure (#13560)
Builds on
7fbdc9f
- Fix: Avoids reinitializing the SpanAggregator on
`tracer.configure(...)` and when an application forks. Instead
`SpanAggregator.reset()` is called. This operation ensures global
configurations are re-applied, trace buffer can be reset, and trace
writer is recreated. This ensures agent based sampling rules are not
reset.
- Clean up
- Removes `writer` parameter from `SpanAggregator.__init__(...)` with
this change the intialization of the global writer is an implementation
detail of the SpanAggregator. There is no longer a need to supply the
`SpanAggregator` with a writer on the initialization of the global
tracer.
- Moves all implementation details of resetting the `SpanAggregator`
from `Tracer.configure(...)` and `Tracer._recreate(...)` to
`SpanAggregator.reset(...)`.
- Removes the initialization of the SpanAggregator from
`_default_span_processors_factory`. With this change the global tracer's
SpanAggregator is never re-created. It's only modified when
`tracer.configure(..)` is used.
- Rename `DatadogSampler._service_based_samplers` property to
`DatadogSampler._agent_based_sampler` to improve clarity. These sampling
rules are no longer supplied via environment variables or a programatic
api, they can only be set by the Datadog Agent.
- Splits `SpanAggregator.trace_proccessors` into two properties
`SpanAggregator.dd_proccessors` and `SpanAggregator.user_processors`.
`SpanAggregator.users_proccessors` is set after application startup via
`Tracer.configure(..)` while `SpanAggregator.dd_proccessors` is internal
to the ddtrace library and should only be set by ddtrace components.
This separation allows us to avoid recreating all trace processors when
`tracer.configure()` is called.
- Adds a more descriptive release note to an unreleased fix.
## Checklist
- [x] PR author has checked that all the criteria below are met
- The PR description includes an overview of the change
- The PR description articulates the motivation for the change
- The change includes tests OR the PR description describes a testing
strategy
- The PR description notes risks associated with the change, if any
- Newly-added code is easy to change
- The change follows the [library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
- The change includes or references documentation updates if necessary
- Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))
## Reviewer Checklist
- [x] Reviewer has checked that all the criteria below are met
- Title is accurate
- All changes are related to the pull request's stated goal
- Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes
- Testing strategy adequately addresses listed risks
- Newly-added code is easy to change
- Release note makes sense to a user of the library
- If necessary, author has acknowledged and discussed the performance
implications of this PR as reported in the benchmarks PR comment
- Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
---------
Co-authored-by: Brett Langdon <[email protected]>
0 commit comments