Skip to content

feat: align admin monitoring and production usage observability - #181

Merged
HansonL622 merged 7 commits into
1024XEngineer:mainfrom
fj-sunny:codex/async-scene-ielts-latency
Aug 27, 2026
Merged

feat: align admin monitoring and production usage observability#181
HansonL622 merged 7 commits into
1024XEngineer:mainfrom
fj-sunny:codex/async-scene-ielts-latency

Conversation

@fj-sunny

Copy link
Copy Markdown
Contributor

Summary

  • align the admin monitoring dashboard with production Grafana metrics, full-width trend rendering, and real current P95 values for scene generation and evaluation endpoints
  • improve official Alibaba Cloud usage ingestion, reconciliation, observability status, billing presentation, and quality governance data
  • preserve legacy Web/mobile telemetry compatibility and audio/IELTS behavior while updating production frontend validation

Validation

  • frontend/admin: 27 tests passed
  • frontend/admin: TypeScript and Vite production build passed
  • backend/unispeaking-server: admin test suite passed
  • production Docker images for backend and admin built and deployed successfully

@fennoai fennoai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The monitoring, usage reconciliation, telemetry compatibility, and frontend contract changes were reviewed. The admin test slice passes, and the web telemetry checks pass; the local web build could not be run because the workspace has no usable vite executable. One monitoring correctness regression is called out inline.

double p95Current = queryPrometheus(p95Query("[24h]")) * 1000;
double p95Previous = queryPrometheus(p95Query("[24h] offset 24h")) * 1000;
GovernanceCounts counts = governanceCounts();
Summary summary = new Summary("UP", queryPrometheus(apiErrorRateQuery()),

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P1] Preserve the Prometheus-backed backend health status

This hard-codes the summary status to UP, so the overview and OverviewPage will continue to show the backend as healthy even when Prometheus reports up == 0 or cannot be reached. The previous implementation derived this field from the up{instance="backend:8080"} metric, and the dashboard still uses this value to choose the normal/error state. Keep the health query (or an equivalent backend health check) here and report DOWN when it fails.

@HansonL622 HansonL622 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@HansonL622
HansonL622 merged commit 9b9520d into 1024XEngineer:main Aug 27, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants