[Doc] Is TraceConfig still relevant? #410
Comments
tigrannajaryan
added a commit
to tigrannajaryan/opentelemetry-proto
that referenced
this issue
Jul 4, 2022
Resolves open-telemetry#410 I am not aware of any OpenTelemetry or non-OpenTelemetry codebase that uses the experimental TraceConfig. I suggest to remove it. It can be added back if we see the need for it in the future. The SDK configuration may also be achieved by different means, see open-telemetry/opentelemetry-specification#2207 We need to keep this PR open for a while and circulate it widely to make sure we give enough opportunity to object the removal.
tigrannajaryan
added a commit
that referenced
this issue
Jul 20, 2022
Resolves #410 I am not aware of any OpenTelemetry or non-OpenTelemetry codebase that uses the experimental TraceConfig. I suggest to remove it. It can be added back if we see the need for it in the future. The SDK configuration may also be achieved by different means, see open-telemetry/opentelemetry-specification#2207 We need to keep this PR open for a while and circulate it widely to make sure we give enough opportunity to object the removal.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello 馃憢 馃檪
Although I find the
TraceConfigresource very interesting, I can't find any concrete usage in the documentation, nor in the protocol...Is it still relevant? Should it be discarded? Or is it part of a future improvement?
Thanks for your work 馃檱
The text was updated successfully, but these errors were encountered: