メニュー
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".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use when scaling a dedicated Kubernetes cluster (Linode LKE or AWS EKS) on Zeabur — listing node pools, changing node counts, or adding/removing node pools. Use when user says "scale my cluster", "add nodes", "remove nodes", "resize node pool", "加節點", "擴容", "縮容". Do NOT use for renting new servers (use zeabur-server-rent) or for single-VM dedicated servers (they have no node pools).
Use when debugging services on a user's dedicated server via SSH. Use when needing to run a command on the server, inspect pods, check container logs, view k8s resources, or run kubectl commands. Use when "service exec" is insufficient and you need server-level access. Use when user says "check my server", "run X on my server", "debug pod", "kubectl", "SSH into server", "check k8s", or "inspect cluster".
Use when renting a new dedicated server. Use when user wants to buy or provision a server. Supports discounted VPS from Linode, DigitalOcean, Hetzner, AWS Lightsail, GCP, Tencent Cloud (騰訊雲), Alibaba Cloud (阿里雲), and Volcano Engine (火山引擎).
Use when managing AI Hub account, API keys, balance, usage, or API endpoints. Use when user says "AI Hub", "add AI credits", "create API key", "check AI usage", "auto-recharge", "AI Hub endpoint", "AI Hub base URL", "how to use AI Hub API", "LLM API", "AI API", "OpenAI compatible", "Anthropic API", "GPT", "Claude", "Gemini", "DeepSeek", or "Grok" in the context of Zeabur.
Use when logging in, logging out, or checking Zeabur auth status. Use when user says "login", "log in", "登入", "logout", "log out", "登出", "auth status", "am I logged in", or "who am I".
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.
SOC 職業分類に基づく
| 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.