Skip Navigation
Show nav
Heroku Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
  • Documentation
  • Changelog
  • More
    Additional Resources
    • Home
    • Elements
    • Products
    • Pricing
    • Careers
    • Help
    • Status
    • Events
    • Podcasts
    • Compliance Center
    Heroku Blog

    Heroku Blog

    Find out what's new with Heroku on our blog.

    Visit Blog
  • Log inorSign up
View categories

Categories

  • Heroku Architecture
    • Dynos (app containers)
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Command Line
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery
    • Continuous Integration
  • Language Support
    • Node.js
    • Ruby
      • Working with Bundler
      • Rails Support
    • Python
      • Background Jobs in Python
      • Working with Django
    • Java
      • Working with Maven
      • Java Database Operations
      • Java Advanced Topics
      • Working with Spring Boot
    • PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Getting Started
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
    • Heroku Data For Redis
    • Apache Kafka on Heroku
    • Other Data Stores
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
    • Compliance
  • Heroku Enterprise
    • Private Spaces
      • Infrastructure Networking
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
      • Heroku Connect Administration
      • Heroku Connect Reference
      • Heroku Connect Troubleshooting
    • Single Sign-on (SSO)
  • Patterns & Best Practices
  • Extending Heroku
    • Platform API
    • App Webhooks
    • Heroku Labs
    • Building Add-ons
      • Add-on Development Tasks
      • Add-on APIs
      • Add-on Guidelines & Requirements
    • Building CLI Plugins
    • Developing Buildpacks
    • Dev Center
  • Accounts & Billing
  • Troubleshooting & Support
  • Integrating with Salesforce
  • Extending Heroku
  • Heroku Labs
  • Getting Started with Heroku Data Labs

Getting Started with Heroku Data Labs

English — 日本語に切り替える

Last updated February 01, 2023

Table of Contents

  • Install or Update the Heroku Data CLI Plugin
  • List Available Experimental Features
  • Enable an Experimental Feature
  • Disable an Experimental Feature

Heroku Data add-ons have experimental features that are under consideration for inclusion in the Heroku platform. By using the data:labs command, you can enable and disable experimental features on your Heroku Data add-on.

Features added through Heroku Data Labs are experimental and subject to change.

Install or Update the Heroku Data CLI Plugin

To use the data:labs command, you must have the latest version of the Heroku Data CLI plugin.

Installing the Heroku Data CLI Plugin

To install the data plugin, use the following CLI command:

$ heroku plugins:install data

Updating the Heroku Data CLI Plugin

The Heroku CLI keeps itself up-to-date automatically. However, if you installed the Debian/Ubuntu package, or used npm install, you must update the CLI manually. To update the data plugin, use the update CLI command:

$ heroku update

List Available Experimental Features

To get a list of experimental features available for your Heroku add-on, use the heroku data:labs:list command:

$ heroku data:labs:list ADDON_NAME
=== Experimental Features Available for ADDON_NAME:

The list command also displays the statuses of available features on your Heroku add-on. For example, if WAL compression is enabled on your Heroku Postgres add-on:

$ heroku data:labs:list postgresql-example-1234
=== Experimental Features Available for postgresql-example-1234:
[+] wal-compression         Write-ahead log compression on Heroku Postgres addons

Enable an Experimental Feature

To enable an experimental feature on your Heroku add-on, use the heroku data:labs:enable command. You must include the --addon flag. You can optionally specify the -a, --app flag for extra detail:

$ heroku data:labs:enable FEATURE --addon=ADDON_NAME -a example-app
Enabling FEATURE on ADDON_NAME... done

Depending on the feature, enabling can take 15 minutes or more. You can check the status by using the heroku data:labs:list command.

Disable an Experimental Feature

Disabling an experimental feature on your Heroku add-on is similar to enabling. Use the heroku data:labs:disable command. The --addon flag is required:

$ heroku data:labs:disable FEATURE --addon=ADDON_NAME -a example-app
Disabling FEATURE on ADDON_NAME... done

Keep reading

  • Heroku Labs

Feedback

Log in to submit feedback.

Heroku Labs: log-runtime-metrics Getting Started with Heroku Labs

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Podcasts
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing

Subscribe to our monthly newsletter

Your email address:

  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Heroku Podcasts
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Facebook
  • Instagram
  • Github
  • LinkedIn
  • YouTube
Heroku is acompany

 © Salesforce.com

  • heroku.com
  • Terms of Service
  • Privacy
  • Cookies
  • Cookie Preferences