Add AgentPond tracing for Genkit language flows#147
Open
marcusschiesser wants to merge 1 commit into
Open
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
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
LLMspans around all six language-learning prompt flowsnpx agentpond@0.5.2 initThe manual spans add operation, provider, model, status, latency, and error metadata without copying prompt text, images, or generated explanations into span attributes. Genkit's own child spans continue to use the same global OpenTelemetry provider.
Why AgentPond
AgentPond complements HanziGraph's Genkit evaluations with per-request production traces stored in its Firebase project. Maintainers can compare latency and failures across six language-learning flows, identify whether a problem occurred in authorization, a named prompt, Vertex Gemini, or structured output, and analyze behavior locally with DuckDB.
Verification
npm run lintinfunctions/npm run buildinfunctions/npm run buildLLMspan shape with an in-memory exportergit diff --checkCredentialed Genkit evaluations and production Firebase Storage export were not run because the contributor environment does not have Vertex or bucket access.