OpenTelemetry support #59
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
kukushechkin
force-pushed
the
comp-338-opentelemetry-support
branch
from
282e69d
to
6c7458f
Compare
kukushechkin
force-pushed
the
comp-338-opentelemetry-support
branch
from
6c7458f
to
5fc54db
Compare
ollityrkko
approved these changes
Nov 24, 2022
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.
The idea is IQM Client does not depend on OpenTelemetry, but if there is an active context (e.g. someone is profiling circuits execution time), it will add necessary headers to the backend request. Mostly used internally by IQM.