heroku-observability

Consolidate Heroku logs, dyno status, releases, and metrics for health triage.

1|1|Updated Mar 6, 2026

Search Tags:#logs #observability #diagnostics #heroku #error-codes #dyno-health

Ready to run

npx skills add https://github.com/eymass/swe-plugin --skill heroku-observability

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: heroku-observability
Source: https://github.com/eymass/swe-plugin/tree/main/skills/heroku-observability
Command: npx skills add https://github.com/eymass/swe-plugin --skill heroku-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires heroku, jq, and includes scripts (resource) components.

What problem does it solve?

Triages Heroku app health and performance data, consolidating logs, dyno status, releases, and metrics to streamline triage and decision making.

Core Features & Use Cases

Health overview: quick snapshot of dynos, releases, add-ons, and error codes within a defined window.
Incident triage: identify root causes by correlating events across logs, metrics, and releases.
Cost and configuration checks: surface changes in dyno formation and add-on plans to detect anomalies.

Quick Start

Run health_snapshot.sh for your Heroku app to generate a health overview.

Frequently Asked Questions about heroku-observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I triage Heroku app health and dyno status during an incident?▼

To triage Heroku app health, you can consolidate logs, dyno status, releases, and metrics to identify root causes by correlating events across these data points. This approach streamlines incident response and decision making.

Do I need the Heroku CLI and jq installed to run observability scripts?▼

Yes, you need the Heroku CLI and jq installed to run observability scripts. These dependencies are required to execute the health, error, release, and metrics scripts that generate a Heroku app health overview.

What is the best way to get a quick health overview of Heroku dynos and add-ons?▼

The best way to get a quick health overview of Heroku dynos and add-ons is to run a health snapshot script. This generates a snapshot of dynos, releases, add-ons, and error codes within a defined time window.

Can I detect Heroku cost anomalies and configuration changes across app formations?▼

Yes, you can detect Heroku cost anomalies and configuration changes by surfacing changes in dyno formation and add-on plans. This capability checks for cost and configuration anomalies across your Heroku apps.

How do I look up Heroku error codes when investigating app logs?▼

To look up Heroku error codes when investigating app logs, you can use a quick reference of error codes provided by the observability scripts. This helps correlate log events and error codes during performance investigations.

Why are my Heroku observability scripts not working when parsing metrics?▼

Heroku observability scripts may not work when parsing metrics if jq is missing from your environment. The scripts require both the Heroku CLI and jq to successfully query and process health, metrics, and release data.