-
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
Initial opentracing bridge #98
Initial opentracing bridge #98
Conversation
170c7ab
to
4d430de
Compare
4a53c56
to
8877950
Compare
254c30c
to
735e554
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. I'd like a high-level comment explaining all the Context
machinery here.
b499dbd
to
6ea7100
Compare
Updated, ready for review, so the "do not review" label can be dropped. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
6ea7100
to
cb8cb0b
Compare
Fixed conflicts. |
cb8cb0b
to
69f2688
Compare
Rebased again to include the deletion of the registry package, so the bridge code needed updates. Squashed the commits. |
69f2688
to
707ea58
Compare
Updated and rebased on top of the current master, so it builds (span interface got link stuff, so test were failing to build). |
// LogFields() function, so when the call to the function gets | ||
// translated to OpenTelemetry AddEvent() function, an empty context | ||
// is passed. | ||
package opentracing // import "go.opentelemetry.io/experimental/bridge/opentracing" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💥 🏅 💥 🏅 💥
This is ready to merge, once the build is fixed again. Sorry, I may be responsible, but since this is a fork I can't edit the branch myself (I think). |
Looks like the problem is from this commit, which is what replaced the Also, super small thing: thoughts on rebasing to get rid of the merge commit? |
I have resolved the conflict but I cannot update this PR. There isn't much we can do other than open a new PR and give credits to @krnowak in the comments. |
Let's just let @krnowak repair it. |
Adding event with timestamp is not yet a part of the OpenTelemetry specification, but this function will come in handy when implementing the OpenTracing bridge.
There are some features missing - setting up links and span kind; context propagation will only work between two OpenTracing bridges.
The tests mostly check various aspects of the cooperation between OpenTracing and OpenTelemetry APIs.
dae9c88
to
60c5d1f
Compare
Fixed and updated. |
Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.29.1 to 1.30.0. - [Release notes](https://github.com/grpc/grpc-go/releases) - [Commits](grpc/grpc-go@v1.29.1...v1.30.0) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Tyler Yahn <[email protected]>
It's very basic. There is a bunch of TODOs. They are more or less:
context.Context
? In opentracing, you basically create a span and then callopentracing.ContextWithSpan
to get the context with the span stored in it. In opentelemetry, you first create a context, then you create a span (creating a span requires passing a context).FinishWithOptions
in opentracing Tracer?