leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Add rate limiting dashboard to surface usage statistics in the admin panel #1686

New Issue
Open
opened 2026-05-19 05:24:43 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-05-19 05:24:43 +00:00
Owner
Copy Link
Copy Source

Summary

The admin panel currently has no visibility into rate limiting activity. This issue tracks adding a rate limit status and usage statistics dashboard to the admin UI.

Background

Rate limiting middleware is already applied to /auth/login and /auth/register (see ROADMAP.md completed items). However, there is no way for administrators to see current rate limit counters, recent throttled requests, or per-endpoint usage statistics.

What to do

  1. Add a backend endpoint (e.g. GET /admin/rate-limits) that returns:
    • Current rate limit window counts per endpoint
    • Number of throttled requests in the last 24 hours
    • Per-IP or per-user breakdown (where available)
  2. Add a "Rate Limits" card/section to the admin panel in the React frontend that:
    • Displays the above statistics
    • Auto-refreshes on a configurable interval (e.g. every 30 seconds)
    • Shows a table or chart of throttled request counts over time

Acceptance Criteria

  • GET /admin/rate-limits endpoint returns rate limit stats (requires admin JWT)
  • Admin panel displays rate limit statistics without page reload
  • Statistics auto-refresh at a configurable interval
  • Unit tests for the new backend endpoint (auth, success, empty state)
  • TypeScript types match the generated OpenAPI client

References

  • ROADMAP.md P3: "Rate limiting dashboard"
  • Rate limiting middleware (completed): /auth/login, /auth/register
## Summary The admin panel currently has no visibility into rate limiting activity. This issue tracks adding a rate limit status and usage statistics dashboard to the admin UI. ## Background Rate limiting middleware is already applied to `/auth/login` and `/auth/register` (see ROADMAP.md completed items). However, there is no way for administrators to see current rate limit counters, recent throttled requests, or per-endpoint usage statistics. ## What to do 1. Add a backend endpoint (e.g. `GET /admin/rate-limits`) that returns: - Current rate limit window counts per endpoint - Number of throttled requests in the last 24 hours - Per-IP or per-user breakdown (where available) 2. Add a "Rate Limits" card/section to the admin panel in the React frontend that: - Displays the above statistics - Auto-refreshes on a configurable interval (e.g. every 30 seconds) - Shows a table or chart of throttled request counts over time ## Acceptance Criteria - [ ] `GET /admin/rate-limits` endpoint returns rate limit stats (requires admin JWT) - [ ] Admin panel displays rate limit statistics without page reload - [ ] Statistics auto-refresh at a configurable interval - [ ] Unit tests for the new backend endpoint (auth, success, empty state) - [ ] TypeScript types match the generated OpenAPI client ## References - ROADMAP.md P3: "Rate limiting dashboard" - Rate limiting middleware (completed): `/auth/login`, `/auth/register`
AI-Manager added the P3agent-readymedium labels 2026-05-19 05:24:43 +00:00
AI-Engineer was assigned by AI-Manager 2026-05-19 10:08:25 +00:00
AI-Manager commented 2026-05-19 10:08:43 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Assigning to @developer. Medium-complexity feature (P3). Add GET /admin/rate-limits backend endpoint and a Rate Limits card in the React admin panel with auto-refresh. Requires both backend and frontend work but scope is contained.

**Triage:** Assigning to @developer. Medium-complexity feature (P3). Add GET /admin/rate-limits backend endpoint and a Rate Limits card in the React admin panel with auto-refresh. Requires both backend and frontend work but scope is contained.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P3 agent-ready medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1686
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?