Documentation

Initialize an InfluxDB stack

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

InfluxDB automatically creates a new stack each time you apply an InfluxDB template without providing a stack ID. To manually create or initialize a new stack, use the influx stacks init command.

Initialize a stack when applying a template

To automatically create a new stack when applying an InfluxDB template don’t provide a stack ID. InfluxDB applies the resources in the template to a new stack and provides the stack ID the output.

influx apply \
  -o example-org \
  -f path/to/template.yml

Manually initialize a new stack

Use the influx stacks init command to create or initialize a new InfluxDB stack.

Provide the following:

  • Organization name or ID
  • Stack name
  • Stack description
  • InfluxDB template URLs
# Syntax
influx stacks init \
  -o <org-name> \
  -n <stack-name> \
  -d <stack-description \
  -u <package-url>

# Example
influx stacks init \
  -o example-org \
  -n "Example Stack" \
  -d "InfluxDB stack for monitoring some awesome stuff" \
  -u https://example.com/template-1.yml \
  -u https://example.com/template-2.yml

Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2