Render Integration
Monitor service health, deploy events, and bandwidth metrics across your Render workloads. Correlate deploys with performance regressions and catch resource exhaustion before services go down.
How It Works
Connect via Render API Key
Generate a Render API key in your account settings and add it to TigerOps. The integration immediately begins discovering all services, databases, cron jobs, and static sites across your Render account.
Configure Deploy Webhook
Add the TigerOps webhook URL to your Render service deploy hooks. Deploy events — started, succeeded, and failed — are correlated with metric changes so you can instantly identify when a deploy caused a regression.
Set Service Health Thresholds
Define per-service CPU, memory, and response time SLOs. TigerOps alerts when Render services approach instance resource limits and predicts when you'll need to scale up based on current growth trends.
Correlate Deploys with Performance
Every Render deploy is tracked as an event marker on TigerOps dashboards. When error rates or latency change after a deploy, TigerOps surfaces the correlation automatically for instant root cause identification.
What You Get Out of the Box
Service Health Monitoring
Track CPU utilization, memory usage, and instance counts for Render web services and background workers. Alert when services approach instance type resource limits that trigger OOM kills or CPU throttling.
Deploy Event Tracking
Capture every Render deploy as an annotated event. Correlate deploy timestamps with error rate, latency, and resource metric changes to identify regressions within seconds of deployment.
Bandwidth & Egress Monitoring
Monitor outbound bandwidth per service and across your entire Render account. Alert on unexpected bandwidth spikes that could indicate data exfiltration, runaway data exports, or misconfigured response sizes.
Cron Job Execution Tracking
Track Render cron job execution results, duration, and missed schedules. Alert when cron jobs fail or when execution time exceeds the next scheduled interval, causing job overlap.
Database & Redis Health
Monitor Render PostgreSQL database CPU, storage, connection counts, and Render Redis memory usage alongside your service metrics for a unified view of your entire Render stack.
AI Root Cause Analysis
When Render service health degrades, TigerOps AI correlates the event with recent deploys, upstream traffic volume changes, database query latency, and infrastructure changes to surface the root cause.
Render API & Webhook Setup
Connect your Render account to TigerOps via API key and deploy webhooks.
# TigerOps Render integration configuration
# Settings > Integrations > Render in TigerOps dashboard
integrations:
render:
apiKey: ${RENDER_API_KEY} # from Render Account Settings > API Keys
# Poll interval for service metrics
pollInterval: 60s
# Services to monitor (empty = all services)
serviceFilter: []
# Environment filter
environments:
- production
- staging
# Per-service SLOs
serviceSLOs:
"api-production":
cpuWarningPct: 70
cpuCriticalPct: 90
memoryWarningPct: 75
memoryWarningMB: 400
"worker-production":
cpuWarningPct: 80
memoryWarningPct: 80
# Add deploy webhook in Render dashboard:
# Service Settings > Deploy Hooks > Add Hook
# URL: https://ingest.atatus.net/webhooks/render/deploy
# Secret: (copy from TigerOps Settings > Integrations > Render)
# TigerOps will then annotate dashboards with deploy events
# and correlate metric changes with specific deployments.Common Questions
How does TigerOps collect metrics from Render services?
TigerOps uses the Render API to collect service metadata and deploy events. For runtime metrics (CPU, memory, bandwidth), TigerOps uses the Render Metrics API endpoint. Deploy webhooks provide real-time deploy event correlation without polling.
Can TigerOps monitor Render private services that are not publicly accessible?
Yes. TigerOps collects metrics via the Render API and webhooks, which work regardless of whether services have a public URL. Private services — internal APIs, workers, and databases — are fully visible in TigerOps.
Does TigerOps track Render auto-scaling events?
Yes. When Render scales a service up or down, TigerOps records the scaling event with the previous and new instance count. This allows you to correlate scaling events with response time and throughput changes to validate that auto-scaling is working as expected.
How do I get alerted when a Render deploy fails?
TigerOps receives deploy failure events via the Render deploy webhook within seconds of the failure. You can configure alert channels (Slack, PagerDuty, email) for deploy failure events, with the option to only alert on production environment failures.
Can TigerOps monitor multiple Render teams or workspaces?
Yes. Add multiple Render API keys — one per team or workspace — to TigerOps. Services are labeled by workspace so you can view cross-team health in unified dashboards while keeping alert routing scoped to the appropriate team.
Stop Discovering Render Service Issues After Deploy
Deploy correlation, service health alerts, and bandwidth monitoring. Connect via API key in 2 minutes.