Initial OpenTelemetry support #254
Merged
Conversation
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
Signed-off-by: Ed Snible <[email protected]>
Member
Author
|
Here is an example showing Jaeger displaying two runs, one where I did not have the Replicate API Key and one where I had the key.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Resolves #250
This PR allows PDL to send telemetry to an OpenTelemetry collector.
The PR includes brief documentation describing how to use Jaeger to view traces.
This PR is intended as a minimum viable project of telemetry support. We don't try to generate relationships between multiple LLM calls, or create custom PDL-specific key=value pairs on spans. We don't provide guidelines for using any tracing visualization tools.