remote-logs

Remote Logs

This skill applies only to apps with a backend/ folder. Frontend-only apps do not produce remote logs.

When an app backend has been deployed using fusebase deploy, you can fetch logs from the cloud:

1. Build logs - Output from the container image build process
2. Runtime logs - Live stdout/stderr and system logs from the running backend

Important Distinction

Context	Command	What It Reads
Local development	fusebase dev start	Log files in <app>/logs/dev-*/
Deployed backend	fusebase remote-logs	Cloud build and runtime logs

If the app is running locally via fusebase dev start, use the dev-debug-logs skill instead.

Commands

Build Logs

Fetch build/deployment logs from the most recent deploy:

fusebase remote-logs build <appId>

Output includes:

• Build status (in_progress, failed, finished)
• Full build log (Dockerfile execution, npm install, etc.)
• Deploy job ID for reference

Runtime Logs

Fetch live logs from the running backend:

# Default: last 100 console (stdout/stderr) entries
fusebase remote-logs runtime <appId>

# Specify tail count (0-300)
fusebase remote-logs runtime <appId> --tail 200

# Get system logs instead of console logs
fusebase remote-logs runtime <appId> --type system

# Filter to a specific container (backend or sidecar)
fusebase remote-logs runtime <appId> --container api
fusebase remote-logs runtime <appId> --container my-sidecar

Options:

• --tail <n> - Number of log entries (0-300, default: 100)
• --type <type> - Log type: console (stdout/stderr) or system (service/infrastructure logs)
• --container <name> - Filter logs to a specific container. Use api for the main backend, or the sidecar name for sidecar containers

Log Format with Sidecars

When an app backend has sidecar containers, runtime logs include output from all containers. Each log line is prefixed with the container name: