// Use when viewing service runtime or build logs. Use when user says "show logs", "why did deploy fail", "check build output", or "debug runtime error".
Use when debugging services on a user's dedicated server via SSH. Use when needing to inspect pods, check container logs, view k8s resources, or run kubectl commands on the server. Use when "service exec" is insufficient and you need server-level access. Use when user says "check my server", "debug pod", "kubectl", "SSH into server", "check k8s", or "inspect cluster".
Use when deploying a local project or codebase to Zeabur. Use when the user says "deploy this", "deploy to Zeabur", "deploy from GitHub", "search my repos", or "find my repository". Default to direct deploy unless the user explicitly asks for Git-based deployment.
Use when the user uploads a project file and you see `<UploadedFile>` in the message. Use when user says "看看這個專案", "分析程式碼", "check this project", "what's in this upload", or asks about the structure of an uploaded file.
Use when modifying service config without full redeploy. Use when updating env vars and restarting single service. Use when user says "change env var", "update config", "fix variable without redeploying", "upgrade service version", "update image tag", or "change service tag".
Use when deploying a database to Zeabur. Use when user needs MySQL, PostgreSQL, MongoDB, or Redis. Use when user says "I need a database", "add database", "deploy postgres", "set up MySQL", "add Redis", "add MongoDB", or "connect to database". Also use when user mentions data persistence issues like "data lost after restart", "data not saved", "data disappears", "need persistent storage for data", or "how to persist data". Also use when integrating a database with an existing service.
Use when deploying object storage (S3-compatible) to Zeabur. Use when user needs MinIO, RustFS, or S3-compatible storage. Use when user says "object storage", "file storage", "S3", "MinIO", "RustFS", "upload files", "store files", "blob storage", or "OSS". Also use when integrating object storage with an existing service.
| name | zeabur-deployment-logs |
| description | Use when viewing service runtime or build logs. Use when user says "show logs", "why did deploy fail", "check build output", or "debug runtime error". |
Always use
npx zeabur@latestto invoke Zeabur CLI. Never usezeaburdirectly or any other installation method. Ifnpxis not available, install Node.js first.
# 1. Get service ID (use the `zeabur-service-list` skill)
npx zeabur@latest service list --project-id <project-id> -i=false
# 2. View runtime logs
npx zeabur@latest deployment log --service-id <service-id> -t runtime -i=false 2>&1 | tail -50
# Runtime logs (CLI auto-resolves the latest deployment if needed)
npx zeabur@latest deployment log --service-id <id> -t runtime -i=false
# Runtime logs for a specific deployment
npx zeabur@latest deployment log --service-id <id> --deployment-id <deployment-id> -t runtime -i=false
# Build logs (CLI auto-resolves the latest deployment if needed)
npx zeabur@latest deployment log --service-id <id> -t build -i=false
# Build logs for a specific deployment
npx zeabur@latest deployment log --deployment-id <deployment-id> -t build -i=false
# Watch logs (live tail)
npx zeabur@latest deployment log --service-id <id> -w -i=false
The CLI automatically resolves the latest deployment when --deployment-id is not provided:
| Scenario | What happens |
|---|---|
Git/Upload service, no --deployment-id | CLI auto-resolves latest deployment → logs returned |
| Pure image service (e.g. Docker image), runtime log | No deployment exists → falls back to prebuilt query → logs returned |
| Pure image service, build log | No deployment exists → returns error (image services have no build logs) |
Explicit --deployment-id provided | Uses the provided ID directly, no auto-resolution |
Use --deployment-id when you need logs from a specific deployment (not the latest). List deployments with:
npx zeabur@latest deployment list --service-id <service-id> -i=false
| Tip | Details |
|---|---|
Use tail -50 | Logs can be verbose, pipe to tail for recent entries |
Use grep to filter | `... 2>&1 |
| Note singular | deployment log not deployment logs |
| Check service status | Look for SERVER STARTED, Ready, listening |
After diagnosing issues from logs, use the zeabur-restart skill to restart the service if needed.