Table of Contents [expand]
Last updated September 03, 2026
To provide additional insights into memory health we offer optional language-specific runtime metrics. JVM, Go (public beta), Node.js (public beta), and Ruby (public beta) are currently supported.
This feature only works for apps that use classic buildpacks. Subscribe to our changelog to stay informed of when we add this feature to apps using Cloud Native Buildpacks.
General Information
For all metrics the resolution is dependent on the timeframe selected. More information on metrics retention and resolution is available in the Application Metrics docs.
Language runtime metrics are available for all dynos using the supported languages, except for eco or fir dynos.
Setup Instructions
First, enable the Language Metrics flag on your application via the dashboard or the CLI. To enable it through dashboard, open the metrics preferences panel and turn on the Enhanced Language Metrics toggle:

Alternatively, enable it through the Heroku CLI:
$ heroku labs:enable "runtime-heroku-metrics" -a "my-app-name"
This toggle tells our metrics collection backend to collect and report any language specific metrics that are exported by your application. Depending on the language, there can be some additional steps you must take to have these metrics exported to our data collection service.
See the language-specific documentation for detailed instructions on exporting your metrics and for more information regarding our available metrics:
- JVM runtime metrics
- Go language metrics (public beta)
- Ruby language metrics (public beta)
- Node.js language metrics (public beta)
Using with Pipelines
To use language runtime metrics with Heroku Pipelines, you must follow the setup instructions for the most downstream app in the pipeline (the one you deploy to before promoting). Then you must enable the feature in the metrics dashboard of any upstream apps in the pipeline before promoting.
If your downstream app is an Eco-tier app, you must follow all of the setup instructions except enabling the feature in the metrics dashboard. For example, you must still add a buildpack or a new dependency to the app. The feature doesn’t work on the Eco app, but any other dyno types downstream can use the feature after you promote.
Sample Metrics


Disabling Metrics Collection
If for any reason you want to stop data collection for additional languages, toggle off the Enhanced Language Metrics toggle via the metrics preferences panel, or by using this CLI command:
$ heroku labs:disable "runtime-heroku-metrics" -a "my-app-name"
Keep in mind that there are gaps in metrics data for any time period that this flag is disabled.