Skip to content

[Admin Console] Phase 2: Live Metrics Dashboard #632

Closed

Description

@Ferryx349

Operators have no way to see relay health at a glance. Checking events per second, active connections, or DB/Redis status requires SSH access and reading raw logs.

  • Add cluster-aware in-memory counters for EPS, accepted/rejected events, and active WebSocket connections
  • Add lightweight DB and Redis health checks
  • Expose metrics via GET /admin/metrics as a Server-Sent Events (SSE) stream for live updates
  • Track CPU and memory load
  • Avoid heavy DB polling, use in-memory counters where possible

Activity

  1. self-assigned this
    on May 31, 2026
  2. Ferryx349 commented on Jun 25, 2026

    @Ferryx349
    CollaboratorAuthor

    So here main scope:- in-memory runtime metrics (EPS, accept/reject, active WS, worker health, DB/Redis), SSE at GET /admin/metrics, admin dashboard UI.

    SQL KPIs (top talkers, events by kind) stay with #439 #464, will embed those in admin later.

    @cameri @kushagra0902 , OK with this split?

  3. kushagra0902 commented on Jun 25, 2026

    @kushagra0902
    Contributor

    So here main scope:- in-memory runtime metrics (EPS, accept/reject, active WS, worker health, DB/Redis), SSE at GET /admin/metrics, admin dashboard UI.

    SQL KPIs (top talkers, events by kind) stay with #439 #464, will embed those in admin later.

    @cameri @kushagra0902 , OK with this split?

    Works for me! Let me know if you need some help with it or some changes in the prev PRs

  4. Ferryx349 commented on Jul 19, 2026

    @Ferryx349
    CollaboratorAuthor

    Completed in #666 #662 #653 and #661

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions