[DO NOT MERGE] POC of propagation for sql server via SET CONTEXT_INFO#508
Closed
[DO NOT MERGE] POC of propagation for sql server via SET CONTEXT_INFO#508
SET CONTEXT_INFO#508Conversation
This file contains hidden or 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
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 PR a prototype to demonstrate how
SET CONTEXT_INFOcan be used in the real world.https://github.com/XSAM/otelsql/pull/508/files#diff-4f427d2b022907c552328e63f137561f6de92396d7a6e8f6c2ea1bcf0db52654R291 is the change for
otelsqlto make this happen.Steps to run the example:
example/sqlserverfolderdocker compose up -dThis runs a sql server, otel collector, jaeger and sql client.docker compose up clientto run a query from sql client. Meanwhile,Example results:
From Jaeger

You will see the trace_id and trace_id from
CONTEXT_INFOis linked to an existing span on Jaeger.