Opyntel
Render

Render monitoring: all your Render services in one dashboard

Render shows metrics one service at a time and alerts only on failures and disk. Opyntel’s Render monitoring shows every service at a glance with latency and error-rate alerts, plus the other systems you run.

See how it works
Built in vs Opyntel

Render on its own, and Render with Opyntel

Feature by feature, the biggest gaps first: what Render gives you, and what you get in one dashboard with Opyntel.

Every service at a glance

On Render

Render shows each service’s usage on that service’s Metrics page, and for a scaled service you can view all of its instances or a subset. The metrics docs describe no page that shows every service in a workspace together.

With Opyntel

Opyntel shows the full list of your services in one table, grouped by project, with down and degraded first. Requests, error rate and latency sit in the same row for every web service, so you see it all at a glance.

Render plus the other systems you run

On Render

Render’s dashboard covers the services in your Render workspace. Anything you run elsewhere is watched somewhere else.

With Opyntel

Opyntel puts Render next to every other platform you connect, from app platforms to edge hosts and your own servers, in one dashboard and one daily situation page that turns yellow or red per service.

Latency percentiles

On Render

Render charts total requests by status code and p50, p75, p90 and p99 response times for web services, and its metrics stream exports p50, p95 and p99. Both need a Pro workspace or higher.

With Opyntel

Opyntel shows requests, status classes, p50, p95 and p99 latency and the 5xx error rate for every public service on a Render Pro workspace and up, side by side across services, so a slow one stands out without opening it.

Alerts when it goes down, and when it recovers

On Render

Render notifies by email or Slack when a build, deploy or cron job fails, a service becomes unhealthy or a persistent disk passes 80%. The only threshold on the notifications page is disk usage, and the unhealthy-service recovery notice goes to Slack only.

With Opyntel

Opyntel alerts out of the box when a service goes down or when CPU, memory, error rate or p95 latency passes your threshold, by email, Slack or SMS depending on your plan. Every alert notifies when it fires and again when it recovers, and custom thresholds per service come with Pro.

History

On Render

Render keeps metrics for 7 days on Hobby, 14 days on Pro and 30 days on Scale and Enterprise.

With Opyntel

Opyntel keeps the same metrics for 30 days on the free plan, a year on Pro and unlimited on Enterprise, whatever your Render plan, so last month’s incident is still there to compare.

Setup

How to set up Render monitoring with Opyntel

Render monitoring in four steps: from Render to one dashboard with everything else you run.

  1. Create a Render API key
    Under API Keys in your Render account settings, create a key and copy it: Render shows it once. A key carries your account’s access, so Opyntel only ever reads with it.
    Create a Render API key
  2. Sign in to Opyntel
    Open your Opyntel dashboard and add a source. Accounts start from the waitlist, so join it to get yours.
  3. Paste the token in your dashboard
    Add Render as a source and paste the key. Opyntel finds the services in every workspace the key can see.
  4. See Render in one dashboard
    Render monitoring lands next to the other platforms you run: every service and server sits in one dashboard, down and degraded first, with default alert rules on from the start.

Don’t see your platform? From your Opyntel account you can request an integration with more platforms. Until then, and tell us which one you run on.

FAQ

Render questions, answered

Short answers; some link to a guide that goes into detail.

The instance went over its instance type’s memory and was restarted. How to fix Render out-of-memory restarts.

No. Render charts requests by status code, but its notifications do not cover error rate. Render 502 and 5xx errors.

Its process exits and Render starts it again; the Events feed and exit code show why. Why a Render service keeps restarting.

Render lists every run of a cron job with its status, and notifications can tell you when a run fails. Opyntel adds runs that never started, next to your other platforms. Why a cron job is not running.

Not on its own. Render charts P50 to P99, but its notifications cover failures, health and disk. How to alert on P95 latency on Render.

Check status.render.com first. If every Render service you run fails at the same moment it is the platform; if one service fails alone it is that service. Opyntel checks your public endpoints from several regions and alerts when one goes down.

The alerts your platform doesn’t send.

One dashboard for everything you run, with the alerts your platforms leave out. Read-only, nothing to install in your apps.

See how it works