-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Remove WithRecording
option from trace API
#192
Comments
Say again |
When we tried to remove this (#223), we found out about the problem discussed in #224. Blocking this until open-telemetry/opentelemetry-specification#307 to be resolved. |
Info from duplicate issue #787
|
WithRecordingEvents
optionWithRecording
option from trace API
…aws (#192) * Bump github.com/aws/aws-sdk-go from 1.33.16 to 1.33.19 in /detectors/aws Bumps [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) from 1.33.16 to 1.33.19. - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Changelog](https://github.com/aws/aws-sdk-go/blob/master/CHANGELOG.md) - [Commits](aws/aws-sdk-go@v1.33.16...v1.33.19) Signed-off-by: dependabot[bot] <support@github.com> * Auto-fix go.sum changes in dependent modules Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: dependabot[bot] <dependabot[bot]@users.noreply.github.com>
…#1660) * Remove `WithRecord()` option from SpanConfig options This brings the trace API into conformance with the specification. * Add entry to CHANGELOG Fixes #192 * Updated CHANGELOG with PR# * Cleaned up CHANGELOG notes * fixup! Merge remote-tracking branch 'upstream/main' into remove-with-record * Use new spanContext API to set traceflags, tracestate Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
This option needs to be removed before the GA release. The specification decision on how to resolve this issue has been postponed until after GA. To reduce the maintenance burden of this code after GA and to ensure we can support the future resolution of this issue at the specification level we need to remove this option.
Work needs to be done to explore how this option can be removed and still conform to the SDK specification sampling.
The text was updated successfully, but these errors were encountered: