mcpField
Z
zeabur-deployment-logs

zeabur-deployment-logs

github.com/zeaburCloud & DevOps39198 installsUpdated 7w ago
Repository

About zeabur-deployment-logs

zeabur-deployment-logs is a skill for retrieving Zeabur service deployment logs with the Zeabur CLI. It covers runtime and build logs, including how the CLI resolves the latest deployment or targets a specified one.

Key features

  1. 01Fetch runtime logs
  2. 02Fetch build logs
  3. 03Resolve the latest deployment automatically
  4. 04Target a specific deployment
  5. 05Filter or tail log output

Use cases

  1. 01Inspect recent service runtime output
  2. 02Review build failures
  3. 03Check logs for a particular deployment

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/zeabur/agent-skills --skill zeabur-deployment-logs

After installing, type/zeabur-deployment-logsin Claude Code to confirm it loaded.

Details

From the project README

Zeabur Deployment Logs

Always use npx zeabur@latest to invoke Zeabur CLI. Never use zeabur directly or any other installation method. If npx is not available, install Node.js first.

Workflow

# 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

Log Types

# 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

DeploymentID Behavior

The CLI automatically resolves the latest deployment when --deployment-id is not provided:

ScenarioWhat happens
Git/Upload service, no --deployment-idCLI auto-resolves latest deployment → logs returned
Pure image service (e.g. Docker image), runtime logNo deployment exists → falls back to prebuilt query → logs returned
Pure image service, build logNo deployment exists → returns error (image services have no build logs)
Explicit --deployment-id providedUses 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

Tips

TipDetails
Use tail -50Logs can be verbose, pipe to tail for recent entries
Use grep to filter`... 2>&1
Note singulardeployment log not deployment logs
Check service statusLook for SERVER STARTED, Ready, listening

After diagnosing issues from logs, use the zeabur-restart skill to restart the service if needed.

Comments

Markdown supported