Add support for propagating OpenTelemetry trace span information over NRI ttrpc connection. #68
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 patch set implements extra runtime/adaptation and plugin/stub NRI options which enable the propagation of OpenTelemetry trace span information over ttrpc connections.
This PR is an alternative to #67. This PR introduces two boolean options which tell NRI whether it internally should set up the necessary ttrpc options to enable otel trace span propagation over ttrpc. This brings in an indirect dependency on [github.com/containerd/]otelttrpc and OpenTelemetry itself.
#67 on the other hand simply opens up the ttrpc client and server used by NRI for extra ttrpc options. This allows one to pass in the necessary options to enable otel trace span propagation (essentially using the same otelttrpc instrumenting ttrpc interceptors as used here), both in NRI enabled runtimes and NRI plugins.
I wanted to ask feedback about which of these alternative approaches others find more preferable, hence I filed both as draft PRs.