dev-log-monitoring

Real-time log monitoring captures output from both Encore.ts backend and SvelteKit frontend services by running them with log redirection, then analyzing streams to track event flow, detect drift, and diagnose agent runs. Start each service with log capture (e.g., `encore run 2>&1 | tee /tmp/backend-logs.txt`), verify health endpoints, and inspect logs for graph stream events and performance patterns across services.

Yes. Playwright MCP integration enables automated navigation of your frontend while you simultaneously inspect console output and network activity for WebSocket stream events. This allows you to trigger user flows, verify real-time event streaming during ScreenGraph runs, and correlate frontend interactions with backend log patterns in a single workflow.

Drift detection diagnostics require analyzing complete agent run flow timelines by cross-referencing backend logs (Encore.ts), frontend logs (SvelteKit), and network streams captured during Playwright-driven navigation. Review logs for stream event gaps, timing mismatches, and service health checks to identify where the observed behavior diverged from expected state.

Health check verification is a prerequisite step before meaningful log analysis. Confirm both backend and frontend services are healthy and responding before beginning drift detection or agent run diagnostics, as unhealthy endpoints will produce incomplete or misleading log patterns that obscure the actual issue.

Log-pattern extraction involves parsing captured logs from both services to identify timing sequences, event ordering, and cross-service latency. Use real-time log capture during test runs, then review consolidated logs for performance bottlenecks, stream delays, and service interaction issues to produce actionable run diagnostics.

Yes. Real-time log monitoring inspects frontend console and network activity for WebSocket stream events, allowing you to verify that event streams are being delivered correctly during agent runs. Gaps or delays in logs indicate stream failures or timing issues affecting ScreenGraph behavior.