feat(dashboard): show custom track-event properties on tool invocations - #67
Merged
Conversation
Coverage Report for dashboard
File Coverage
|
||||||||||||||||||||||||||||||||||||||||||||
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.
Why
Integrators that disable input/output capture — for privacy policies or app-store requirements — report curated fields through
yavio.track()instead. Those events land in ClickHouse (events.metadata) but the dashboard never rendered them anywhere. The result: a privacy-conscious integration's invocations all show "No input/output data captured for this invocation", and the data it deliberately does send (e.g. Shipal'scarrier,status,user_intent,latency_ms) is invisible.What
A custom
track()event fired inside a tool handler shares the invocation'strace_id(the SDK's AsyncLocalStorage trace context). The expanded invocation row in the tool-detail view now:trackevents for the listed traces (one extra paged query,trace_id IN (...), same time window — a track event shares its call's timestamp to within the handler's runtime)metadatawhen non-empty (Properties)Values are integrator-supplied content and are rendered as plain text only.
Tests
queryToolRecentInvocations: joins custom events by trace id (dedup, empty-trace skip, mapping to the right invocations) — 3 new/updated casesRider
Second commit adds
.claude/settings.local.jsonto.gitignore(personal Claude Code settings; must never land in a public repo).Verified against production data: Shipal Prod events confirm the two-events-per-trace shape this renders.