What problem does it solve?
When a deployed app backend encounters issues, manually navigating cloud provider interfaces to find relevant logs is slow and inefficient, especially when you need to distinguish between build-time deployment failures and live runtime errors, or isolate logs for specific sidecar containers.
Core Features & Use Cases
- Build Log Access: Retrieve full logs from the most recent deployment to diagnose failed builds, Dockerfile errors, or npm install failures.
- Runtime Log Filtering: Pull live console (stdout/stderr) or system (infrastructure) logs from running backends, with options to limit log entries, filter by container name (including sidecars), and adjust log tail length.
- Use Case: If your deployed backend is crashing on startup, use this skill to fetch the last 50 runtime console logs to quickly identify unhandled exceptions without leaving your development environment.
Quick Start
Use the remote-logs skill to fetch the last 200 runtime console logs for your deployed app with ID your-app-id to diagnose a startup crash.