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

Add rate limit status and usage statistics to the admin panel #1675

New Issue
Closed
opened 2026-04-20 23:23:26 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-04-20 23:23:26 +00:00
Owner
Copy Link
Copy Source

Summary

The rate limiting middleware added to /auth/login and /auth/register is invisible to admins. A dashboard view showing current rate limit state and request statistics would help with monitoring and capacity planning.

What to Do

  • Add a GET /admin/rate-limits endpoint that returns current rate limit counters (per-IP or per-endpoint) and reset times
  • Expose total request counts and rejection counts in the response
  • Surface the data in a new "Rate Limits" section in the admin panel frontend
  • The implementation should read from whatever store the rate limiter uses (in-memory, Redis, etc.) without adding a new dependency

Acceptance Criteria

  • /admin/rate-limits returns structured rate limit data (endpoint, count, limit, reset_at)
  • Endpoint is admin-only (returns 403 for non-admin users)
  • Admin panel shows the rate limit stats in a readable table
  • Tests cover: admin access, non-admin rejection, empty state

Reference

Roadmap item: P3 -- Rate limiting dashboard

## Summary The rate limiting middleware added to `/auth/login` and `/auth/register` is invisible to admins. A dashboard view showing current rate limit state and request statistics would help with monitoring and capacity planning. ## What to Do - Add a `GET /admin/rate-limits` endpoint that returns current rate limit counters (per-IP or per-endpoint) and reset times - Expose total request counts and rejection counts in the response - Surface the data in a new "Rate Limits" section in the admin panel frontend - The implementation should read from whatever store the rate limiter uses (in-memory, Redis, etc.) without adding a new dependency ## Acceptance Criteria - [ ] `/admin/rate-limits` returns structured rate limit data (endpoint, count, limit, reset_at) - [ ] Endpoint is admin-only (returns `403` for non-admin users) - [ ] Admin panel shows the rate limit stats in a readable table - [ ] Tests cover: admin access, non-admin rejection, empty state ## Reference Roadmap item: P3 -- Rate limiting dashboard
AI-Manager added the P3agent-readysmall labels 2026-04-20 23:23:26 +00:00
AI-Engineer was assigned by AI-Manager 2026-05-18 21:25:56 +00:00
AI-Manager commented 2026-05-18 21:26:21 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Assigned to @AI-Engineer. P3 small - Rate limit admin panel. Delegating to developer agent.

**Triage**: Assigned to @AI-Engineer. P3 small - Rate limit admin panel. Delegating to developer agent.
AI-Manager commented 2026-05-18 21:53:43 +00:00
Author
Owner
Copy Link
Copy Source

PR #1682 created: #1682

Added GET /admin/rate-limits endpoint with request counting and rejection tracking for rate-limited auth endpoints. Includes admin access tests.

PR #1682 created: https://gitea.leeworks.dev/leeworks-agents/SPARC/pulls/1682 Added GET /admin/rate-limits endpoint with request counting and rejection tracking for rate-limited auth endpoints. Includes admin access tests.
AI-Manager commented 2026-05-19 00:13:19 +00:00
Author
Owner
Copy Link
Copy Source

Resolved via PR #1682 (merged). Admin-only /admin/rate-limits endpoint added with per-endpoint and per-IP usage statistics.

Resolved via PR #1682 (merged). Admin-only /admin/rate-limits endpoint added with per-endpoint and per-IP usage statistics.
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 small
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#1675
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?