Install
$ agentstack add skill-render-oss-skills-render-monitor ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Monitor Render Services
Real-time monitoring of Render services including health checks, performance metrics, and logs.
When to Use This Skill
Activate this skill when users want to:
- Check if services are healthy
- View performance metrics
- Monitor logs
- Verify a deployment is working
- Investigate slow performance
- Check database health
Prerequisites
MCP tools (preferred): Test with list_services() - provides structured data
CLI (fallback): render --version - use if MCP tools unavailable
Authentication: For MCP, use an API key (set in the MCP config or via the RENDER_API_KEY env var, depending on tool). For CLI, verify with render whoami -o json.
Workspace: get_selected_workspace() or render workspace current -o json
> Note: MCP tools require the Render MCP server. If unavailable, use the CLI for status and logs; metrics and database queries require MCP.
MCP Setup
If list_services() fails, set up the Render MCP server. For detailed per-tool walkthroughs, see render-mcp.
Quick setup: Add the Render MCP server to your AI tool's MCP config:
- URL:
https://mcp.render.com/mcp - Auth header:
Authorization: Bearer - API key:
https://dashboard.render.com/u/*/settings#api-keys
After configuring, restart your tool and retry list_services(). Then set your workspace with list_workspaces() / get_selected_workspace().
Quick Health Check
Run these 5 checks to assess service health:
# 1. Check service status
list_services()
# 2. Check latest deploy
list_deploys(serviceId: "", limit: 1)
# 3. Check for errors
list_logs(resource: [""], level: ["error"], limit: 20)
# 4. Check resource usage
get_metrics(resourceId: "", metricTypes: ["cpu_usage", "memory_usage"])
# 5. Check latency
get_metrics(resourceId: "", metricTypes: ["http_latency"], httpLatencyQuantile: 0.95)
Service Health
Check Status
list_services()
get_service(serviceId: "")
Check Deployments
list_deploys(serviceId: "", limit: 5)
| Status | Meaning | |--------|---------| | live | Deployment successful | | build_in_progress | Building | | build_failed | Build failed | | deactivated | Replaced by newer deploy |
Check Errors
list_logs(resource: [""], level: ["error"], limit: 50)
list_logs(resource: [""], statusCode: ["500", "502", "503"], limit: 50)
Performance Metrics
CPU & Memory
get_metrics(
resourceId: "",
metricTypes: ["cpu_usage", "memory_usage", "cpu_limit", "memory_limit"]
)
| Metric | Healthy | Warning | Critical | |--------|---------|---------|----------| | CPU | 85% | | Memory | 90% |
HTTP Latency
get_metrics(
resourceId: "",
metricTypes: ["http_latency"],
httpLatencyQuantile: 0.95
)
| p95 Latency | Status | |-------------|--------| | 1s | Problem |
Request Count
get_metrics(
resourceId: "",
metricTypes: ["http_request_count"]
)
Filter by Endpoint
get_metrics(
resourceId: "",
metricTypes: ["http_latency"],
httpPath: "/api/users"
)
Detailed metrics guide: [references/metrics-guide.md](references/metrics-guide.md)
Database Monitoring
PostgreSQL Status
list_postgres_instances()
get_postgres(postgresId: "")
Connection Count
get_metrics(resourceId: "", metricTypes: ["active_connections"])
Query Database
query_render_postgres(
postgresId: "",
sql: "SELECT state, count(*) FROM pg_stat_activity GROUP BY state"
)
Find Slow Queries
query_render_postgres(
postgresId: "",
sql: "SELECT query, mean_exec_time FROM pg_stat_statements ORDER BY mean_exec_time DESC LIMIT 10"
)
Key-Value Store
list_key_value()
get_key_value(keyValueId: "")
Log Monitoring
Recent Logs
list_logs(resource: [""], limit: 100)
Error Logs
list_logs(resource: [""], level: ["error"], limit: 50)
Search Logs
list_logs(resource: [""], text: ["timeout", "error"], limit: 50)
Filter by Time
list_logs(
resource: [""],
startTime: "2024-01-15T10:00:00Z",
endTime: "2024-01-15T11:00:00Z"
)
Stream Logs (CLI)
render logs -r --tail -o text
Quick Reference
MCP Tools
# Services
list_services()
get_service(serviceId: "")
list_deploys(serviceId: "", limit: 5)
# Logs
list_logs(resource: [""], level: ["error"], limit: 100)
list_logs(resource: [""], text: ["search"], limit: 50)
# Metrics
get_metrics(resourceId: "", metricTypes: ["cpu_usage", "memory_usage"])
get_metrics(resourceId: "", metricTypes: ["http_latency"], httpLatencyQuantile: 0.95)
get_metrics(resourceId: "", metricTypes: ["http_request_count"])
# Database
list_postgres_instances()
get_postgres(postgresId: "")
query_render_postgres(postgresId: "", sql: "SELECT ...")
get_metrics(resourceId: "", metricTypes: ["active_connections"])
# Key-Value
list_key_value()
get_key_value(keyValueId: "")
CLI Commands (Fallback)
Use these if MCP tools are unavailable:
# Service status
render services -o json
render services instances
# Deployments
render deploys list -o json
# Logs
render logs -r --tail -o text # Stream logs
render logs -r --level error -o json # Error logs
render logs -r --type deploy -o json # Build logs
# Database
render psql # Connect to PostgreSQL
# SSH for live debugging
render ssh
Healthy Service Indicators
| Indicator | Healthy | Warning | Critical | |-----------|---------|---------|----------| | Deploy Status | live | update_in_progress | build_failed | | Error Rate | 1% | | p95 Latency | 2s | | CPU Usage | 90% | | Memory Usage | 95% |
References
- Metrics guide: [references/metrics-guide.md](references/metrics-guide.md)
Related Skills
- render-deploy — Deploy new applications to Render
- render-debug — Diagnose and fix deployment failures
- render-mcp — MCP server setup and tool catalog
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: render-oss
- Source: render-oss/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.