-
Notifications
You must be signed in to change notification settings - Fork 59
docs(tracing): explain how spans reach the developer UI traces tab - #427
Open
michaelxu2288 wants to merge 1 commit into
Open
docs(tracing): explain how spans reach the developer UI traces tab #427michaelxu2288 wants to merge 1 commit into
michaelxu2288 wants to merge 1 commit into
Conversation
Nothing exports spans until a tracing processor is registered. The guide only showed the SGP processor, which disables itself without SGP credentials, so a reader following it locally saw an empty traces tab. Document the Agentex processor (AgentexTracingProcessorConfig) that writes to the backend /spans API. Claude-Session: https://claude.ai/code/session_01HCVKnA7LeJZ44nxZz1uzF3
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.
Uh oh!
There was an error while loading. Please reload this page.
What
observability_and_tracing.mdonly showed registering the SGP processor. Nothing exports spans until a processor is registered, and the SGP processor disables itself without SGP credentials, so a reader following the guide locally saw an empty traces tab. Adds a "Seeing spans in the developer UI" section forAgentexTracingProcessorConfig(writes to the backend/spansAPI) and reframes the SGP section as additive.Companion to scale-agentex-python PR "fix(templates): register the local Agentex tracing processor".
https://claude.ai/code/session_01HCVKnA7LeJZ44nxZz1uzF3
The documentation-only change appears safe to merge, with no concrete correctness, security, or repository-rule violations identified.
Summary
AgentexTracingProcessorConfig.Reviews (1) · Last reviewed commit: "docs(tracing): explain how spans reach t..."