-
Notifications
You must be signed in to change notification settings - Fork 0
Implement Agent Observability Core Features - Dashboard and Sessions with Real-Time Data #49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-authored-by: tikazyq <3393101+tikazyq@users.noreply.github.com>
Co-authored-by: tikazyq <3393101+tikazyq@users.noreply.github.com>
Co-authored-by: tikazyq <3393101+tikazyq@users.noreply.github.com>
|
@copilot propose next steps |
Based on the current implementation, here are the recommended next steps prioritized by value and effort: 🎯 Immediate Next Steps (High Value, Medium Effort)1. Add Real-Time Updates (WebSocket/SSE)Why: Dashboard currently requires manual refresh. Real-time updates would make the platform feel alive.
2. Session Details PageWhy: Users can see sessions but can't dive into details. This is needed for debugging and analysis.
3. Multi-Project SupportWhy: Currently hardcoded to
🚀 Medium-Term Goals (High Value, Higher Effort)4. Advanced Filtering UIWhy: API supports filtering but no UI controls exist.
5. Go Collector IntegrationWhy: Complete the collector implementation (20% done) to enable real agent data collection.
6. Analytics DashboardWhy: Raw data exists but no insights/trends.
📊 Long-Term Enhancements7. Performance Optimizations
8. Enhanced Visualizations
9. Testing & Quality
Recommendation: Start with #1 (Real-Time Updates) and #2 (Session Details) as they provide immediate user value and complement the current implementation well. |
|
@copilot let's update docs with current progress and next steps |
…admap Co-authored-by: tikazyq <3393101+tikazyq@users.noreply.github.com>
Updated documentation with current progress and detailed roadmap in commit 17d182b. What's New:
Key Documents:
Immediate Priorities:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR implements Phase 1 of the agent observability core features, transforming the dashboard and sessions pages from static placeholders into functional real-time monitoring displays. The implementation includes new API routes for data retrieval, React server components for display, and comprehensive documentation with a detailed 9-phase roadmap for future development.
Key Changes:
- Added three new API endpoints (
/api/dashboard/stats,/api/dashboard/activity,/api/sessions) that integrate with existing core services - Created six React server components for dashboard metrics, activity timeline, and session displays
- Updated dashboard and sessions pages to use dynamic data fetching with Suspense boundaries
Reviewed Changes
Copilot reviewed 15 out of 15 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
docs/dev/20251022-agent-observability-core-features/README.md |
Comprehensive user guide documenting the new features, API endpoints, architecture, and usage instructions |
docs/dev/20251022-agent-observability-core-features/NEXT_STEPS.md |
Detailed 9-phase roadmap with prioritized features and implementation plans |
docs/dev/20251022-agent-observability-core-features/IMPLEMENTATION_SUMMARY.md |
Technical implementation details and design decisions documentation |
docs/dev/20251021-codebase-reorganization/README.md |
Updated to reference the new agent observability implementation |
apps/web/components/agent-observability/sessions/sessions-list.tsx |
Reusable server component for displaying session lists with filtering |
apps/web/components/agent-observability/sessions/index.ts |
Export barrel for sessions components |
apps/web/components/agent-observability/dashboard/recent-activity.tsx |
Server component displaying recent agent events timeline |
apps/web/components/agent-observability/dashboard/index.ts |
Export barrel for dashboard components |
apps/web/components/agent-observability/dashboard/dashboard-stats.tsx |
Server component displaying four key dashboard metrics |
apps/web/components/agent-observability/dashboard/active-sessions.tsx |
Server component showing currently running agent sessions |
apps/web/app/sessions/page.tsx |
Updated to use new SessionsList component with Suspense |
apps/web/app/dashboard/page.tsx |
Updated to use new dashboard components with Suspense |
apps/web/app/api/sessions/route.ts |
New API endpoint for session listing with filtering support |
apps/web/app/api/dashboard/stats/route.ts |
New API endpoint providing aggregated dashboard metrics |
apps/web/app/api/dashboard/activity/route.ts |
New API endpoint returning recent agent events |
| import { NextRequest, NextResponse } from 'next/server'; | ||
| import { AgentSessionService, AgentEventService } from '@codervisor/devlog-core/server'; | ||
|
|
||
| export async function GET(request: NextRequest) { |
Copilot
AI
Oct 22, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The request parameter is declared but never used. Consider removing it if not needed, or use _request to indicate it's intentionally unused.
| export async function GET(request: NextRequest) { | |
| export async function GET(_request: NextRequest) { |
| export async function GET(request: NextRequest) { | ||
| try { | ||
| const searchParams = request.nextUrl.searchParams; |
Copilot
AI
Oct 22, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The function parameter request is only used to extract searchParams. Consider destructuring directly or using _request if the full request object might be needed for future middleware.
| export async function GET(request: NextRequest) { | |
| try { | |
| const searchParams = request.nextUrl.searchParams; | |
| export async function GET({ nextUrl }: NextRequest) { | |
| try { | |
| const searchParams = nextUrl.searchParams; |
Overview
This PR implements Option 1 from PR #48 recommendations: building out the core agent observability features. The dashboard and sessions pages have been transformed from placeholder content into fully functional real-time monitoring displays with live data integration.
What's New
🎯 Enhanced Dashboard (
/dashboard)The main landing page now displays:
🔍 Enhanced Sessions View (
/sessions)The sessions page now provides:
🔌 Backend API Routes
Three new API endpoints power the frontend with real-time data:
GET /api/dashboard/stats{ "success": true, "data": { "activeSessions": 3, "totalEventsToday": 145, "averageDuration": 2700000, "eventsPerMinute": 2.4 } }GET /api/dashboard/activity?limit=20Returns recent agent events with type, agent ID, timestamp, and context (e.g., file paths).
GET /api/sessions?status=active&limit=50Returns sessions with filtering support for agent type, outcome, status, and date ranges.
Technical Implementation
Architecture
All new components are React Server Components that fetch data server-side for better performance and SEO. The architecture follows this flow:
Key Features
AgentSessionServiceandAgentEventServiceFile Structure
Validation
Metrics
Documentation
Three comprehensive documents added/updated:
Current Status
Phase 1: Foundation Complete ✅ (October 22, 2025)
Known Limitations
projectId: 1(TODO: Query across all user's projects)Next Steps
See NEXT_STEPS.md for the complete prioritized roadmap. Immediate priorities:
Phase 2: Interactive Features (1-2 weeks)
/sessions/[id]route with full event timeline (2-3 days)Phase 3: Enhanced Filtering & Search (2-3 weeks)
Phase 4: Analytics & Insights (3-4 weeks)
Phase 5: Performance & Quality (Ongoing)
Related
docs/dev/20251022-agent-observability-core-features/Status: Phase 1 complete with comprehensive documentation and clear roadmap
Impact: Dashboard and sessions pages are now fully functional with real-time agent monitoring. Foundation established for 9-phase development roadmap.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.