Setting the file. One moment.
Subchapter 27.10
references/telemetry-dashboard.mdMarkdown4 KBView on GitHub
Reproducible definition of the media-use usage dashboard. The dashboard answers
“how much is media-use used, for what, is reuse working, and what can’t it
satisfy” from the telemetry scripts/lib/telemetry.mjs already emits. Build it
in an authorized HyperFrames analytics project; this doc is the source of truth
so it can be recreated. Local complement: (same questions,
from + , no dashboard access needed).
scripts/11 filesAlso bundled
Gitignoreresolve --stats.media/~/.mediaEvents attribute to the same person as the hyperframes CLI and studio
— the shared install id in ~/.hyperframes/config.json (anonymousId), stitched
to the HeyGen account ($identify, distinct_id = email/username) on sign-in.
Not fully anonymous by design; pseudonymous before sign-in, account-linked after.
$ip:null. Opt-out: HYPERFRAMES_NO_TELEMETRY=1 / DO_NOT_TRACK=1 (also CI, dev).
Every event carries surface: "media-use". Event properties are coarse —
never intent text, file names, or paths.
| Event | Fires on | Key properties |
|---|---|---|
media_use_resolve | a resolve that produced/returned an asset | type, source, provider, via, local_only, provider_override |
media_use_resolve_miss | a resolve that found nothing | type, local_only, provider_override (no intent) |
media_use_candidates | --candidates / --dry-run listing | type, counts |
media_use_doctor_run | --doctor | ok, checks_failed, failed[] |
media_use_compare | grade-compare / compare | command, cells, truncated, total, render_ready_timed_out |
media_use_transcribe · media_use_duck · media_use_transcript_cut | audio-engine ops | op-specific |
query-trends, count of media_use_resolve over time (daily). “How much.”media_use_resolve broken down by type (bgm/sfx/image/icon/logo/voice/grade/lut). “For what.”A / (A + B) where A = media_use_resolve, B = media_use_resolve_miss. “Is the catalog covering needs.”media_use_resolve broken down by provider; a second tile by via (url / params-fallback / params) to catch CDN→params LUT downgrades.media_use_resolve_miss broken down by type (the tuning signal — pair with local resolve --stats, which also shows the missed intents that telemetry deliberately omits).media_use_doctor_run broken down by failed[] (which dependency check fails most) + checks_failed distribution.media_use_compare by command, plus truncated / render_ready_timed_out rates (observe before lifting the 16-cell cap).first_run property ships (plan U5), segment media_use_resolve first-run vs repeat.For each tile, confirm the event/property schema, build its trend or breakdown,
then add it to a dashboard. Keep names prefixed media-use: so the dashboard is
greppable. Cross-surface note: because identity is shared with CLI/studio, you
can also break these down by the same person across cli_command* and studio:*
events.