fix(observability): restore historical continuity in the AI Usage and GPU Metrics dashboards

[JSONbored]

Summary

• Follow-up to fix(observability): restore historical continuity in the Self-Host dashboard #6779/fix(test): update grafana dashboard assertions for the historical-continuity query rewrite #6787 (which fixed grafana/dashboards/gittensory.json): the same refactor(observability): hard-cutover rename gittensory_ metric prefix to loopover_ #5522 hard-cutover rename touched all 10 dashboard JSON files, with no gittensory_ fallback anywhere. Audited the other 9 — 7 use SQL, third-party exporter metrics (node_*, pg_stat_*), or other datasources that were never gittensory-prefixed, so only ai-usage.json (9 queries) and gpu-metrics.json (5 queries, 3 underlying metrics) needed the fix.
• Applied the same (loopover_x or gittensory_x) union pattern, carefully avoiding the label-matcher-after-closing-paren bug found and fixed in fix(test): update grafana dashboard assertions for the historical-continuity query rewrite #6787 — every rewritten query validated directly against live Prometheus before deploying, confirming both metric names carry real historical series.
• gpu-metrics.json had no existing test file at all; added one scoped to this fix.
• Deployed both fixes live to edge-nl-01 and restarted Grafana to force a clean reprovision — confirmed via provisioning logs, no errors.

Scope

• Narrow, single-purpose change (2 dashboards + their tests, same bug class)
• No secrets/private terms touched
• No changelog edit

Validation

• npx vitest run test/unit/selfhost-grafana-ai-usage-dashboard.test.ts test/unit/selfhost-grafana-gpu-metrics-dashboard.test.ts — 13/13 passing
• Every rewritten query confirmed valid + returning real data against live production Prometheus before deploying
• Confirmed zero remaining un-unioned loopover_ai_*/loopover_ai_provider_* queries in either file, and zero label-after-paren syntax issues

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.63%. Comparing base (e275417) to head (acb5597).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6804   +/-   ##
=======================================
  Coverage   93.63%   93.63%           
=======================================
  Files         683      683           
  Lines       68148    68148           
  Branches    18703    18703           
=======================================
  Hits        63812    63812           
  Misses       3350     3350           
  Partials      986      986           

Flag	Coverage Δ
shard-1	43.57% <ø> (-0.06%)	⬇️
shard-2	36.88% <ø> (+0.15%)	⬆️
shard-3	32.75% <ø> (ø)
shard-4	33.64% <ø> (-0.57%)	⬇️
shard-5	31.46% <ø> (-0.11%)	⬇️
shard-6	45.88% <ø> (+0.20%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[loopover-orb]

Warning

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-17 07:16:28 UTC}

4 files · 1 AI reviewer · 2 blockers · CI green · clean

⏸️ Suggested Action - Manual Review

Review summary
This PR extends the (loopover_x or gittensory_x) union pattern from the already-merged #6787 fix to two more dashboards (ai-usage.json, gpu-metrics.json) that lost historical continuity in the #5522 rename. The label-matcher placement is correct in every rewritten expression — {provider="codex"} is applied inside each individual rate()/increase() call rather than after the closing paren of the union, avoiding the exact bug #6787 fixed. Tests assert byte-for-byte expected expressions and include a regex guard against the label-after-paren regression, and a new test file was added for gpu-metrics.json which previously had none.

Nits — 4 non-blocking

• Several expressions now have redundant double-wrapping parens, e.g. ai-usage.json:294 `sum by (provider) ((loopover_ai_cost_usd_total or gittensory_ai_cost_usd_total)) or vector(0)` — harmless but slightly noisier PromQL than necessary.
• The PR description references related PRs (fix(observability): restore historical continuity in the Self-Host dashboard #6779/fix(test): update grafana dashboard assertions for the historical-continuity query rewrite #6787) and an originating issue (refactor(observability): hard-cutover rename gittensory_ metric prefix to loopover_ #5522) but doesn't explicitly cite an open tracking issue being closed by this PR; worth confirming this is maintainer-authorized follow-up work rather than unsolicited scope.
• Consider a lightweight regex-based normalization pass across all remaining dashboards on a schedule, rather than manual audits, to catch any future renames automatically.
• In test/unit/selfhost-grafana-gpu-metrics-dashboard.test.ts, the long chain of near-duplicate `targets.some(...)` assertions could be table-driven (array of expected exprs + `for` loop) to reduce repetition.

Concerns raised — review before merging

• No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.
• Maintainer requires a linked issue — Link the relevant issue (for example Closes #123) before opening the PR.

📋 Copy for AI agents — paste into your coding agent

Fix the following blocker(s) from this PR review:

1. No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.

2. Maintainer requires a linked issue — Link the relevant issue (for example `Closes #123`) before opening the PR.

Decision drivers

• ❌ Code review — 2 blockers (1 reviewer)
• ❌ Gate result — Blocking (Repo-configured hard blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 33 registered-repo PR(s), 26 merged, 332 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 33 PR(s), 332 issue(s).
Improvement	ℹ️ Insufficient signal	risk: clean · value: insufficient-signal · LLM: moderate

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: Python, TypeScript, Ruby, Go, JavaScript, MDX, Shell, Solidity
• Official Gittensor activity: 33 PR(s), 332 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Start here: Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Then work through the remaining 2 steps in the Signals table above.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review