Skip to main content

​
Overview

Heroku log drains forward your application’s stdout/stderr to Squasher over HTTPS. Squasher detects error patterns and groups them with AI triage automatically. No SDK, no code changes, no redeployment required. If you use the Log Connectors screen in Squasher, create the Heroku connector first and copy the managed endpoint and ingest key from there. The manual URL below uses the same drain destination shape.

​
Setup

1

Install the Heroku CLI

If you haven’t already, install the Heroku CLI.
2

Add the Squasher drain

Replace YOUR_PROJECT_ID with your Squasher project ID and your-heroku-app with your Heroku app name.
3

Verify

Trigger an error in your app. Within seconds, it appears in your Squasher dashboard.Check the drain is working:

​
What Gets Captured

Squasher ingests all Heroku log lines but only creates error groups from:
  • Lines with severity error, fatal, critical, or err
  • Lines containing error indicators: Error, Exception, panic, fatal, SIGKILL
  • Heroku platform errors (H10, H12, H13, H14, R14, etc.)
All other log lines are stored for context to enrich AI triage.

​
Heroku Log Format

Heroku log drains forward syslog-framed messages. Squasher parses the standard Heroku log format:

​
Combining with SDK

Use both a log drain and an SDK for maximum coverage:
  • Log drain catches infrastructure errors (OOM kills, dyno crashes, routing errors)
  • SDK provides rich context (stack traces, breadcrumbs, user info)
Squasher deduplicates by fingerprint, so the same error won’t be counted twice.

​
Agent handoff