Heroku Integration
Monitor dyno memory and CPU, router latency, H-error codes, release events, and add-on performance across your Heroku applications. One drain command to get started.
How It Works
Add a Log Drain
Run a single heroku drains:add command to forward your Heroku application and router log streams to TigerOps. All dyno metrics, request logs, and error events are parsed automatically.
Enable Dyno Metrics
TigerOps parses Heroku log-runtime-metrics lines to extract per-dyno memory usage, CPU load, and swap metrics. No buildpack changes required — just enable the feature flag on your app.
Configure Add-on Forwarding
Connect Heroku Postgres, Redis, and Kafka add-on metrics through the Heroku Platform API. TigerOps enriches add-on metrics with application context for correlated root cause analysis.
Set Scaling Policies
TigerOps monitors dyno utilization and recommends scaling decisions. Set alerts for sustained memory pressure, P95 router latency thresholds, and H-error code spikes to trigger on-call pages.
What You Get Out of the Box
Dyno Memory & CPU
Per-dyno RSS memory, memory quota usage, swap utilization, and CPU load average. TigerOps tracks memory growth trends and predicts R14 memory quota exceeded errors before they occur.
Router Latency & Error Codes
Heroku router connect time, service time, P95/P99 request latency, and H-error code distribution (H10, H12, H13, H14). Identify dyno restarts and timeout cascades instantly.
Log Drain Parsing
Structured log ingestion from the Heroku log stream. TigerOps auto-parses router, dyno, Heroku platform, and application log lines into structured metrics and searchable log events.
Release & Deploy Tracking
Heroku release events are automatically ingested as deployment markers on your TigerOps dashboards. Correlate every metric change with the exact release that caused it.
Add-on Performance
Heroku Postgres connection counts, query latency, and index cache hit rate. Heroku Redis eviction rates and memory usage. All correlated with your application request traces.
Autoscaling Insights
Track Heroku autoscaler events, dyno formation changes, and scale-to-zero events. TigerOps identifies scaling inefficiencies and recommends optimal dyno counts based on traffic patterns.
heroku drains:add Setup
Add the TigerOps log drain to your Heroku app in one command. Enable runtime metrics for full dyno visibility.
# Step 1: Add the TigerOps syslog drain to your Heroku app
heroku drains:add "syslog+tls://ingest.atatus.net:6514?token=YOUR_TIGEROPS_API_KEY" --app your-app-name
# Verify the drain was added
heroku drains --app your-app-name
# Step 2: Enable log-runtime-metrics for dyno CPU/memory data
heroku labs:enable log-runtime-metrics --app your-app-name
# Step 3 (optional): Enable runtime dyno metadata for richer labels
heroku labs:enable runtime-dyno-metadata --app your-app-name
# Step 4: Set config vars for application-level APM (optional)
heroku config:set TIGEROPS_API_KEY="your_api_key" TIGEROPS_SERVICE_NAME="your-app-name" TIGEROPS_ENVIRONMENT="production" --app your-app-name
# Step 5: For Heroku Postgres add-on metrics — connect via Platform API
curl -X POST https://api.atatus.net/v1/integrations/heroku -H "Authorization: Bearer ${TIGEROPS_API_KEY}" -d '{"heroku_oauth_token": "your_heroku_oauth_token", "app_name": "your-app-name"}'Common Questions
Does TigerOps work with Heroku without installing a buildpack?
Yes. The log drain approach requires no buildpack changes. You get router metrics, H-error codes, and release events immediately. To add dyno CPU/memory metrics, you need to enable the log-runtime-metrics lab feature on your Heroku app, which also requires no buildpack.
Can TigerOps monitor multiple Heroku apps and pipelines?
Yes. You can add log drains from multiple Heroku apps to TigerOps. Each app is auto-labeled using the Heroku app name, and you can group apps into logical services, environments (staging, production), or pipelines for unified dashboards.
Does TigerOps support Heroku Private Spaces?
Yes. TigerOps supports Heroku Private Spaces with log drain forwarding over HTTPS. The TigerOps log drain endpoint uses mutual TLS and the standard Heroku syslog drain format accepted by Private Space networking rules.
How does TigerOps handle Heroku R14 and R15 memory errors?
TigerOps parses R14 (memory quota exceeded) and R15 (memory quota greatly exceeded) events from the log stream and fires alerts immediately. It also tracks the memory trend leading up to the error, giving you context on which code path caused the memory growth.
Can I use TigerOps with Heroku Postgres without sharing database credentials?
Yes. TigerOps uses the Heroku Platform API with OAuth scopes to pull Heroku Postgres metrics. No database credentials are required — TigerOps reads metrics from the Heroku-managed metrics endpoint using your Heroku OAuth token.
Full Visibility Into Your Heroku Applications
No credit card required. One drain command to start. Dyno metrics, router latency, and release tracking immediately.