Table: heroku_dyno - Query Heroku Dynos using SQL

A Heroku Dyno is a lightweight, isolated container that runs the command specified in the Procfile of your app. Each dyno belongs to a specific application and is scoped to the environment of that application. Dynos can be used to run virtually any language or service and can be scaled individually based on the needs of the application.

Table Usage Guide

The heroku_dyno table provides insights into the dynos running within a Heroku application. As a developer or DevOps engineer, you can use this table to explore dyno-specific details, such as current status, type, and configuration. This information can be critical for troubleshooting application issues, optimizing resource usage, and understanding the overall health and performance of your Heroku applications.

Important Notes

List queries require an app_name.
Get queries require an app_name and a dyno id.
Pagination is not currently supported for this resource type in the SDK.

Examples

List all dynos

Explore which dynos are currently in use within a specific Heroku application. This is useful for monitoring your app's resource usage and performance.

select
  id,
  name,
  type,
  size,
  state
from
  heroku_dyno
where
  app_name = 'steampipe';

select
  id,
  name,
  type,
  size,
  state
from
  heroku_dyno
where
  app_name = 'steampipe';

List all crashed dynos

Uncover the details of application failures by identifying instances where an application's dynamic components, or 'dynos', have crashed. This can assist in troubleshooting and improving the stability of the application.

select
  id,
  name,
  type,
  size,
  state
from
  heroku_dyno
where
  app_name = 'steampipe'
  and state = 'crashed';

select
  id,
  name,
  type,
  size,
  state
from
  heroku_dyno
where
  app_name = 'steampipe'
  and state = 'crashed';

List all hobby size dynos

Explore which dynos within a specific Heroku application are designated as 'Hobby' size. This can help you understand the resource allocation and usage within your application.

select
  id,
  name,
  type,
  size,
  state
from
  heroku_dyno
where
  app_name = 'steampipe'
  and size = 'Hobby';

select
  id,
  name,
  type,
  size,
  state
from
  heroku_dyno
where
  app_name = 'steampipe'
  and size = 'Hobby';

Schema for heroku_dyno

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form.
account_id	text	=, !=, ~~, ~~, !~~, !~~	Unique identifier of an account.
app	jsonb		App formation belongs to.
app_name	text	=	App name formation belongs to.
attach_url	text		A URL to stream output from for attached processes or null for.
command	text		Command used to start this process.
created_at	timestamp with time zone		When dyno was created.
id	text	=	Unique identifier of this dyno.
name	text		The name of this process on this dyno.
release	jsonb		App release of the dyno.
size	text		Dyno size (default: standard-1X).
sp_connection_name	text	=, !=, ~~, ~~, !~~, !~~	Steampipe connection name.
sp_ctx	jsonb		Steampipe context in JSON form.
state	text		Current status of process (either: crashed, down, idle, starting, or up)
type	text		Type of process.
updated_at	timestamp with time zone		When process last changed state.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- heroku

You can pass the configuration to the command with the --config argument:

steampipe_export_heroku --config '<your_config>' heroku_dyno