zeabur-service-metric
Original：🇺🇸 English
Translated
Use when diagnosing service performance issues. Use when user says "service is slow", "high CPU", "out of memory", "check resource usage", "monitor service", or "why is my service lagging".
9installs
Sourcezeabur/agent-skills
Added on
NPX Install
npx skill4agent add zeabur/agent-skills zeabur-service-metricTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Zeabur Service Metrics
Always useto invoke Zeabur CLI. Never usenpx zeabur@latestdirectly or any other installation method. Ifzeaburis not available, install Node.js first.npx
Check Metrics
bash
# CPU usage
npx zeabur@latest service metric CPU --id <service-id> -i=false
# Memory usage
npx zeabur@latest service metric MEMORY --id <service-id> -i=false
# Network I/O
npx zeabur@latest service metric NETWORK --id <service-id> -i=falseUse to change the time window (default: 2 hours):
--hour <N>bash
npx zeabur@latest service metric CPU --id <service-id> --hour 24 -i=falseDiagnostic Workflow
When a user reports a slow or unresponsive service, check metrics before restarting:
bash
# 1. Get service ID (use the `zeabur-service-list` skill)
npx zeabur@latest service list --project-id <project-id> -i=false
# 2. Check CPU — is the service compute-bound?
npx zeabur@latest service metric CPU --id <service-id> -i=false
# 3. Check memory — is the service running out of RAM?
npx zeabur@latest service metric MEMORY --id <service-id> -i=false
# 4. Check network — is there unusual traffic?
npx zeabur@latest service metric NETWORK --id <service-id> -i=false
# 5. Check logs for errors (use the `zeabur-deployment-logs` skill for details)
npx zeabur@latest deployment log --id <service-id> -i=falseThen decide the action based on evidence:
| Symptom | Likely cause | Action |
|---|---|---|
| CPU consistently near 100% | Compute-bound workload | Upgrade plan or optimize code |
| Memory climbing until OOM | Memory leak or undersized plan | Restart with |
| Network spikes | Traffic surge or external API issues | Check logs for request patterns |
| All metrics normal | Application-level bug | Check deployment logs |