When a Reel workflow crosses the FastAPI backend, asynchronous workers, Redis, and the Next.js frontend, debugging can easily turn into checking several terminals and service logs. Issue #25 brings those events into Reel Quick itself.
The new Application Logs view provides a single place to inspect recent backend and worker activity as it happens. It loads recent history from Redis Streams, then keeps the page updated through Server-Sent Events (SSE).
What Changed
Reel Quick now writes structured Python log events to the Redis Stream reelquick:system:logs. Each event includes a timestamp, severity, service, source, message, and relevant context such as a video or job ID.
The control panel has been refocused into a live log viewer with:
- Recent log history and live updates.
- Severity filters for debug, info, warning, error, and critical events.
- Service filters for the backend and all current workers.
- Expandable exception details for failures.
- Newest events displayed first, so failures are immediately visible.
Redis stays private to trusted server-side components. The Next.js server proxies the protected FastAPI log endpoints, which means the browser never receives Redis credentials or the logging API key.
This turns failures such as unavailable workers, failed media processing, and request errors into visible operational signals instead of messages hidden in separate service logs.
Watch the Demo
See the logging flow in action: Reel Quick Application Logs demo on YouTube.
Explore the Project
Reel Quick is open source: github.com/ronin1770/reel-quick.
Top comments (0)