Align Grafana dashboards with registered metric names

[greatest0fallt1me]

Summary

docs/dashboards/soroban-billing.json and docs/grafana-dashboard-billing-deduct.json query metric names that must match registrations in src/metrics.ts and src/metrics/registry.ts, but there is no check or documentation of the mapping.

Why this matters

Dashboards that silently show 'No data' during incidents are worse than none.

Scope

Document each panel's metric in docs/dashboards/README.md and add a script or test that parses dashboard JSON expressions and asserts every metric name is registered.

Relevant code in CalloraOrg/Callora-Backend:

• docs/dashboards/README.md
• docs/dashboards/soroban-billing.json
• docs/grafana-dashboard-billing-deduct.json
• src/metrics.ts

Priority

Low

Acceptance criteria

• Every metric referenced in dashboard JSON is registered in code
• docs/dashboards/README.md lists panels and metrics
• The check runs in the unit test suite
• Renamed metrics are updated in the dashboards

Validation

Run the new check via npm test -- src/__tests__/billingDeductMetrics.test.ts or a dedicated test.

Non-goals

• Typo-only, formatting-only, or cosmetic changes.
• Unrelated refactors, dependency upgrades, or broad rewrites.
• Removing safeguards or weakening validation to make tests pass.

Contributor application

Before coding, describe the affected modules, proposed state/invariant changes, test strategy, compatibility considerations, and an estimate. Wait for assignment before starting implementation.

PR requirements

Use a feature branch and include Closes #<issue-number>. Address every criterion, map criteria to code and tests, explain security and failure-mode handling, and ensure CI passes.

Quality review

A maintainer will assess correctness, completeness, test depth, compatibility, observability, and adverse-case handling. A substantive implementation is required; merge or CI status alone does not guarantee reward eligibility.

---

Generated by Claude Code

[shobhamerabacha-star]

Hi everyone,

I would love to take this on. My planned approach:

• Build out the handlers for Align Grafana dashboards with registered metric names ensuring proper HTTP status codes and error propagation.
• Add integration test suites for standard invocations and boundary/error conditions.

Looking forward to collaborating on this—please assign!

[Bobai100]

@Bobai100 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi Maintainer,
I hope you’re doing well.
I would really appreciate the opportunity to work on this issue. Having carefully reviewed the acceptance criteria, I’m confident that I can work on it and submit a PR after being assigned.
Please kindly consider assigning this issue to me. I would be grateful for the opportunity to contribute.
Thank you very much for your time and consideration.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Bobai100 to this issue.

[eeshasalaudeen734-creator]

@eeshasalaudeen734-creator has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello Maintainer, I understand the blocker for scalability. I’ll add gap-free backfill and externalize in-memory maps to Redis. Ready to start immediately.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @eeshasalaudeen734-creator to this issue.

[bridgetthnkechi87-cloud]

@bridgetthnkechi87-cloud has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello Maintainer,
I would like to work on this issue. I’m ready to start now and resolve the issue timely.
Please assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @bridgetthnkechi87-cloud to this issue.

[drips-wave]

Congratulations, @eeshasalaudeen734-creator! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @eeshasalaudeen734-creator: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊