tracing: allow the Resource to be set externally
#4472
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@milas could you fix the DCO failure? Looks like your commit misses a DCO sign-off 🙈 |
This is a workaround for the brittleness when constructing OTel `Resource` objects. Internally, the OTel libraries do their own detection which can be merged with one created in code. However, the `semconv` spec versions must match. (NOT module version! the `semconv` package has multiple subpackages for each spec version, e.g. `semconv/v1.17`, `semconv/v1.21`, etc.) This creates a problem when BuildKit is used as a library - the importing app might be using a different, otherwise compatible version of the OTel libraries, so when it creates a resource, it will be merged with one of a different version. By allowing the `Resource` to be set (like the `Recorder`), the calling code can construct a resource using known consistent library versions that work, and then allow BuildKit to take over the rest of the initialization process for OTel. Signed-off-by: Milas Bowman <milas.bowman@docker.com>
milas
force-pushed
the
v0.12-otel-resource
branch
from
b7632c1
to
7b3fe03
Compare
|
Oops, fixed and removed from draft. Hopefully CI is happy 🤞🏻 |
|
Looks like it is! I was planning to update my Moby PR to see if this works (temporarily vendoring from your fork 👍) |
3 tasks
tonistiigi
approved these changes
Dec 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a workaround for the brittleness when constructing OTel
Resourceobjects. Internally, the OTel libraries do their own detection which can be merged with one created in code. However, thesemconvspec versions must match. (NOT module version! thesemconvpackage has multiple subpackages for each spec version, e.g.semconv/v1.17,semconv/v1.21, etc.)This creates a problem when BuildKit is used as a library - the importing app might be using a different, otherwise compatible version of the OTel libraries, so when it creates a resource, it will be merged with one of a different version.
By allowing the
Resourceto be set (like theRecorder), the calling code can construct a resource using known consistent library versions that work, and then allow BuildKit to take over the rest of the initialization process for OTel.See also: