You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Telemetry: specific failure categories for first-run install #1422
project.dev.install failures today only set failed_step from installFailedStep(currentStep). Early failures all look like system:install, so the dashboard cannot tell why installs drop
off.
The classification issue adds a structured failure record. This issue is only about emitting it as telemetry.
Scope
On project.dev.installfailure, set tags from the failure record:
failed_step ← failingStep (including the new startup step when applicable)
new tag, e.g. failure_category ← category
optional: retryable if useful for analysis
Reuse conventions in internal/tracking/events.go. Values stay a closed enum.
Update docs/TELEMETRY.md (tag names, example values, privacy: no credentials, hosts, SQL, or raw detail in tags).
Extend internal/tui/dev/telemetry_test.go: early failures do not default to system:install; tags never contain secret-like strings.
Acceptance criteria
A failed install records a specific failure_category, not only a coarse step.
failed_step uses the classification issue’s bucketing (pre-Start: ≠ system:install).
The dashboard can distinguish major system:install failure reasons via the category tag.
Activity