client_logs: background device diagnostics collection #8
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/client-logs-telemetry"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Backend half of feedback 2 §4 — a place for prod devices to report diagnostics I can query without attaching a debugger.
client_logscollection (1788000000_client_logs.js):user(relation),kind,event,message,meta(json),appVersion,platform,device,ts,created. Rules: owner-create-only, everything else null (superuser-read-only) — devices can append their own rows and nobody but an admin can read them.client_logs.pb.js): nightly cron trims rows older than 14 days (diagnostics, not an archive).docs/telemetry-contract.md): the event catalogue (uncaught,exo_error,av_delay_applied,session_summary), the exact curl to query it as superuser, and the privacy guarantees — the client redacts stream URLs toscheme://hostand never sends an addon token or full signed URL.The app side (TelemetryService, ring buffer, redaction, kill switch, the player signals) is amber-app PR #82. Once this deploys,
av_delay_applied+session_summary.stallsgive real fleet data on the "a track falls behind" reports.🤖 Generated with Claude Code