Feature: API Request Logging & Monitoring Dashboard

[shalinisingh0510]

Description

Currently, the platform provides backend services and API generation, but there is no visible way for developers to monitor or debug API activity.

To improve developer experience and make the platform more production-ready, implement an API request logging and monitoring system. This will allow users to track incoming requests, debug issues, and analyze usage patterns.

⚙️ Proposed Functionality
Log API requests with details such as:
Endpoint
Method (GET, POST, etc.)
Status code
Response time
Timestamp
Create a simple dashboard UI where users can:
View recent API requests
Filter logs by endpoint or status
Identify failed requests (4xx, 5xx)
🎯 Benefits
Helps developers debug APIs easily
Improves transparency of backend operations
Makes the platform more reliable and production-friendly
Adds a professional touch similar to tools like Firebase / Supabase

[yash-pouranik]

@shalinisingh0510
Yes this looks something good and implemetable.

Can u please share ur approach?

one more thing, that basic analytics are already builtin in file
apps/web-dashboard/src/pages/Analytics.jsx
and
apps/web-dashboard/src/pages/ProjectDetails.jsx

what updates will u do? what chaneges?

So, If you are confident about working on this, just let me know, I will assign this issue to u.

[shalinisingh0510]

Thanks for the response! Yes, I’ve gone through the existing analytics implementation in:

• apps/web-dashboard/src/pages/Analytics.jsx
• apps/web-dashboard/src/pages/ProjectDetails.jsx

I understand that basic analytics (like aggregated insights) are already available. My approach will focus on extending this into a request-level logging and monitoring system, which complements—not replaces—the current analytics.

---

🔧 Proposed Approach

1. Backend Enhancements (Core Logging Layer)

• Introduce a request logging middleware that captures:

  • Endpoint
  • HTTP Method
  • Status Code
  • Response Time
  • Timestamp

• Store logs in a structured format (DB collection or logging service).

• Ensure minimal performance overhead (async logging / batching if needed).

---

2. API Design for Logs

Create endpoints like:

• GET /logs → Fetch recent API logs
• GET /logs?endpoint=/api/users&status=500 → Filter logs
• Optional: pagination & limit support for scalability

---

3. Frontend Enhancements (Dashboard UI)

Instead of creating a completely separate system, I’ll extend the current analytics pages:

Updates to Analytics.jsx

• Add a new section/tab: "API Logs"

• Show:

  • Total requests
  • Error rate (4xx, 5xx)
  • Avg response time (basic aggregation from logs)

Updates to ProjectDetails.jsx

• Add a real-time / recent requests table

• Columns:

  • Endpoint | Method | Status | Response Time | Timestamp

• Add filters:

  • By endpoint
  • By status code (focus on failed requests)

---

4. UI/UX Considerations

• Highlight failed requests (4xx/5xx) with colors
• Keep UI clean and consistent with existing design
• Lightweight and fast (no heavy graphs initially)

---

Key Difference from Existing Analytics

• Current system → Aggregated insights (high-level)
• Proposed system → Granular request-level visibility (debugging-focused)

This makes the platform more production-ready, similar to Firebase / Supabase logging dashboards.

---

Scope & Future Extensions (Optional)

• Live streaming logs (WebSockets)
• Download/export logs
• Alerts for high error rates

---

I’m confident about implementing this and keeping it aligned with the current architecture and UI.

Let me know if this approach looks good — I’d love to work on this!

Also if you want i can create multiple issue for that so that tracking will be easier

[yash-pouranik]

Exactly I was thinking the same to create multiple sub issue. I am assigning this to you.
but complete the backend part while completing this issue after co pleting the backend, create a bee issue for its frontend, aaj hi create krdo to me assign krdu accordingly. And start working on backend. All the best.

[yash-pouranik]

@shalinisingh0510

[shalinisingh0510]

@yash-pouranik sure

[yash-pouranik]

Please create the frontend subissue and ping me there @shalinisingh0510

[yash-pouranik]

@shalinisingh0510
Where u have done? - let me know

[yash-pouranik]

I will close this issue by this night if you don't reply @shalinisingh0510