render-monitor

Monitor Render service health, performance metrics, logs, and database status.

Updated Jul 15, 2026

Search Tags:#monitoring #postgresql #logs #metrics #mcp #health check #render

Ready to run

npx skills add https://github.com/greenmartialarts/EventCore --skill render-monitor-greenmartialarts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: render-monitor
Source: https://github.com/greenmartialarts/EventCore/tree/main/.junie/skills/render-monitor
Command: npx skills add https://github.com/greenmartialarts/EventCore --skill render-monitor-greenmartialarts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It gives operators a structured way to check whether Render-hosted services are healthy, diagnose slow performance, and inspect logs and database state without manually navigating the Render dashboard. ## Core Features & Use Cases - Health Checks: Run a five-step quick check covering service status, latest deploy, error logs, CPU/memory usage, and p95 latency. - Metrics Analysis: Query CPU, memory, HTTP latency, request counts, and database connections with documented healthy/warning/critical thresholds. - Log & Database Monitoring: Search and filter logs by level, status code, text, or time range, and query PostgreSQL directly for slow queries and connection stats. - Use Case: After a deploy, verify the service is live, confirm error rates are below 0.1%, and check p95 latency stays under 500ms before declaring the release healthy. ## Quick Start Check the health of my Render web service and show me any recent errors and current CPU and memory usage.

Frequently Asked Questions about render-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check if my Render service is healthy?▼

Run a five-step health check: list services for status, check the latest deploy, pull recent error logs, and query CPU, memory, and p95 HTTP latency metrics. Healthy indicators are a live deploy, error rate under 0.1%, and p95 latency under 500ms.

How do I view Render service logs and filter errors?▼

Use the list_logs MCP tool with the service ID, filtering by level such as error, by status codes like 500 or 503, by search text, or by time range. If MCP is unavailable, use the CLI command render logs with the service ID and level flags.

What metrics can I monitor for Render services?▼

Available metrics include cpu_usage, memory_usage, http_latency at chosen quantiles, http_request_count, bandwidth_usage, instance_count, and active_connections for databases. Each metric has documented healthy, warning, and critical thresholds in the metrics reference guide.

Does Render monitoring work without the MCP server?▼

Partially. The Render CLI can handle service status, deployments, and logs as a fallback, but metrics queries and direct PostgreSQL queries require the Render MCP server configured with an API key.

How do I find slow queries in a Render PostgreSQL database?▼

Use the query_render_postgres MCP tool to run SQL against pg_stat_statements, ordering by mean execution time to surface the slowest queries. You can also check active connection counts against your plan's limits.

Why is my Render service showing high CPU or memory usage?▼

High CPU often comes from inefficient code or missing caching, while high memory can indicate leaks or large in-memory data. Compare usage against the plan limit to assess throttling or OOM risk, then optimize queries, add caching, or scale the plan.