Client: execution graphs tracing using opentelemetry #146
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
pacomf
approved these changes
Feb 2, 2023
|
Added and tracked in separate issue #160 |
|
@IceKhan13 sorry that I couldn't check this on time. I assume that we need to modify the configuration for infrastructure too. Can you create me an issue for that? 🙏 |
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.
Summary
Client: execution graphs tracing using opentelemetry.
This PR introduces tracing of all execution workflows.
In order to enable tracing user need to provide env variable
OT_JAEGER_HOST_KEYto ray node.Programs and separate remote functions are traced.
Details
Screen shot of traced benchmark program.
Resource requirements and (width, depth) of quantum circuits passed are logged into trace info.
Closes #149