fix: telemetry blind spot — 78% of usage had zero completion data#84
Merged
fix: telemetry blind spot — 78% of usage had zero completion data#84
Conversation
These 3 commands account for 78% of all usage (813 run + 735 diff + 13 watch events today) but fire only command_run — never command_complete. This means we get zero enrichment data: no gate results, no tool counts, no health scores, no target IDs, no execution times. Now all three fire command_complete with full enrichment: - run: servers, tools, prompts, resources, gate, health, connect time - diff: gate, target, health score - watch: servers, tools, gate, health, check statuses Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
🎉 This PR is included in version 0.20.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
1 participant
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.
The problem
Today's telemetry (excluding our sessions):
78% of real user activity produces no actionable data. We know someone ran
runordiffbut not: what server they tested, whether it passed, how many tools it has, how long it took, or what their health score was.The fix
Added
recordEvent(buildEvent("command_complete", ...))with full enrichment to:run(legacy command used by GitHub Action) — servers, tools, prompts, resources, gate, health, connect time, check statusesdiff— gate, target ID, health scorewatch— servers, tools, gate, health, check statusesImpact
Once users pick up this version, we'll go from knowing "someone ran a command" to knowing:
3 files changed, +51 lines. 302/302 tests pass.
🤖 Generated with Claude Code