Skip to content

fix: stabilize monitoring pagination and realtime counts#157

Merged
seakee merged 2 commits into
mainfrom
fix/monitoring-pagination-stream-counts
May 29, 2026
Merged

fix: stabilize monitoring pagination and realtime counts#157
seakee merged 2 commits into
mainfrom
fix/monitoring-pagination-stream-counts

Conversation

@seakee
Copy link
Copy Markdown
Owner

@seakee seakee commented May 29, 2026

Summary

Fix monitoring account pagination and realtime row counts after v1.5.2.

Cause

Account summary pagination could be clamped back by stale remote page responses. Realtime rows also reused final stream totals, causing all rows in the same stream to show the same total call count.

Solution

  • Add per-event realtime stream metrics in the usage service.
  • Use per-event stream counts and recent patterns for realtime row display.
  • Prevent stale account page responses from overriding the requested page.
  • Add regression coverage for account pagination and realtime stream counts.

Testing

  • go test ./...
  • npm run type-check
  • npm test

Fixes #154.
Fixes #155.

seakee added 2 commits May 29, 2026 15:24
Add per-event stream counters and recent patterns for paginated realtime rows.

Keep final stream aggregates while exposing row-specific metrics for accurate monitoring display.

Refs #155.
Prevent stale remote account pages from clamping user pagination back to the previous page.

Render realtime rows with per-event stream counts instead of duplicating final stream totals across all rows.

Fixes #154.

Fixes #155.
@seakee seakee merged commit c303741 into main May 29, 2026
3 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

1 participant