Opyntel
Heroku

Heroku monitoring: all your Heroku apps in one dashboard

Heroku shows metrics one app at a time and alerts only on Professional and Fir dynos. Opyntel’s Heroku monitoring shows every app at a glance with alerts on every plan, plus the other systems you run.

See how it works
Built in vs Opyntel

Heroku on its own, and Heroku with Opyntel

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

Every app at a glance

On Heroku

Heroku’s Application Metrics live on each app’s Metrics tab, so you open apps one by one. The main dashboard shows a 24-hour summary of web metrics and sparklines only for apps you mark as favorites.

With Opyntel

Opyntel shows the full list of your apps and dynos in one table, grouped by project, with down and degraded first. Requests, error rate and latency sit in each row, so you see it all at a glance without opening any app.

Latency and error rate

On Heroku

For web dynos, Heroku charts median, p95, p99 and max response time and throughput by status class, plus memory and load or CPU for every process type. Eco dynos have no application metrics.

With Opyntel

Opyntel shows requests, status classes, p50, p95 and p99 latency and the 5xx error rate for every public app, side by side with the services you run on other platforms.

Alerts when it goes down, and when it recovers

On Heroku

Heroku threshold alerts watch p95 response time and the share of 5xx responses, by email, PagerDuty or dashboard notification, and send a final notice when the error state resolves. They need Professional (standard and performance) or Fir dynos.

With Opyntel

Opyntel alerts on any dyno type when a dyno 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 critical ones re-notify hourly.

History

On Heroku

Heroku keeps up to 7 days of metrics. Basic dynos get 24 hours at 10-minute resolution.

With Opyntel

Opyntel keeps the same metrics for 30 days on the free plan, a year on Pro and unlimited on Enterprise, whatever dyno type you run.

Deploys on one timeline

On Heroku

Heroku draws deployment markers on each app’s metrics plots and lists config changes and restarts in that app’s Events table.

With Opyntel

Opyntel puts every deploy with its commit on one activity timeline across all your apps and the other platforms you run, so a bad release lines up with the alert it caused.

The total cost of your app

On Heroku

Heroku shows the month’s balance under Current Usage on your account’s Billing tab, updated nightly, and metered add-on usage on an app’s Resources tab.

With Opyntel

Opyntel shows spend per app and per project on Pro, next to the cost of the other platforms you run, so you see the total cost of your app at a glance. Monthly budget alerts and forecasts come with Enterprise.

Setup

How to set up Heroku monitoring with Opyntel

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

  1. Create a Heroku token with the read scope
    Run heroku authorizations:create --scope read for a direct authorization. The read scope covers your apps and dynos and leaves out config vars and account details.
    Create a Heroku API token with the read scope
  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 Heroku as a source and paste the token. For response times, errors and dyno memory, add the log drain your dashboard shows with heroku drains:add.
  4. See Heroku in one dashboard
    Heroku 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

Heroku questions, answered

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

The response time 19 in 20 requests beat. Heroku charts it, with the median and P99, for web dynos. P50 vs P95 vs P99 latency explained.

heroku logs --tail -a <app> streams the app’s log, and --dyno web follows one process type. Heroku keeps only the most recent lines, so add a log drain if you need history.

Check status.heroku.com first. If every app you run fails together it is the platform; if one app fails alone, look at its dynos and its H error codes. Opyntel checks your public endpoints from several regions and alerts when one goes down.

heroku ps:restart -a <app> restarts every dyno, and naming one, as in heroku ps:restart web.1, restarts only that dyno. Opyntel is read-only and never restarts anything, but it alerts when a dyno crashes.

Dynos are billed by type for the time they run, and add-ons such as Heroku Postgres and Key-Value Store bill on top. Opyntel shows spend per app next to your other platforms with Opyntel Pro.

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