Documentation

Use InfluxDB templates

Use the influx command line interface (CLI) to summarize, validate, and apply templates from your local filesystem and from URLs.

Use InfluxDB community templates

The InfluxDB community templates repository is home to a growing number of InfluxDB templates developed and maintained by others in the InfluxData community. Apply community templates directly from GitHub using a template’s download URL or download the template.

When attempting to access the community templates via the URL, the templates use the following as the root of the URL:

https://raw.githubusercontent.com/influxdata/community-templates/master/

For example, the Docker community template can be accessed via:

https://raw.githubusercontent.com/influxdata/community-templates/master/docker/docker.yml

View InfluxDB Community Templates

View a template summary

To view a summary of what’s included in a template before applying the template, use the influx template command. View a summary of a template stored in your local filesystem or from a URL.

# Syntax
influx template -f <FILE_PATH>

# Example
influx template -f /path/to/template.yml
# Syntax
influx template -u <FILE_URL>

# Example
influx template -u https://raw.githubusercontent.com/influxdata/community-templates/master/linux_system/linux_system.yml

Validate a template

To validate a template before you install it or troubleshoot a template, use the influx template validate command. Validate a template stored in your local filesystem or from a URL.

# Syntax
influx template validate -f <FILE_PATH>

# Example
influx template validate -f /path/to/template.yml
# Syntax
influx template validate -u <FILE_URL>

# Example
influx template validate -u https://raw.githubusercontent.com/influxdata/community-templates/master/linux_system/linux_system.yml

Apply templates

Use the influx apply command to install templates from your local filesystem or from URLs.

Apply templates to an existing stack

To apply a template to an existing stack, include the stack ID when applying the template. Any time you apply a template without a stack ID, InfluxDB initializes a new stack and all new resources. For more information, see InfluxDB stacks.

Apply a template from a file

To install templates stored on your local machine, use the -f or --file flag to provide the file path of the template manifest.

# Syntax
influx apply -o <INFLUX_ORG> -f <FILE_PATH>

# Examples
# Apply a single template
influx apply -o example-org -f /path/to/template.yml

# Apply multiple templates
influx apply -o example-org \
  -f /path/to/this/template.yml \
  -f /path/to/that/template.yml

Apply all templates in a directory

To apply all templates in a directory, use the -f or --file flag to provide the directory path of the directory where template manifests are stored. By default, this only applies templates stored in the specified directory. To apply all templates stored in the specified directory and its subdirectories, include the -R, --recurse flag.

# Syntax
influx apply -o <INFLUX_ORG> -f <DIRECTORY_PATH>

# Examples
# Apply all templates in a directory
influx apply -o example-org -f /path/to/template/dir/

# Apply all templates in a directory and its subdirectories
influx apply -o example-org -f /path/to/template/dir/ -R

Apply a template from a URL

To apply templates from a URL, use the -u or --template-url flag to provide the URL of the template manifest.

# Syntax
influx apply -o <INFLUX_ORG> -u <FILE_URL>

# Examples
# Apply a single template from a URL
influx apply -o example-org -u https://example.com/templates/template.yml

# Apply multiple templates from URLs
influx apply -o example-org \
  -u https://example.com/templates/template1.yml \
  -u https://example.com/templates/template2.yml

Apply templates from both files and URLs

To apply templates from both files and URLs in a single command, include multiple file or directory paths and URLs, each with the appropriate -f or -u flag.

# Syntax
influx apply -o <INFLUX_ORG> -u <FILE_URL> -f <FILE_PATH>

# Example
influx apply -o example-org \
  -u https://example.com/templates/template1.yml \
  -u https://example.com/templates/template2.yml \
  -f ~/templates/custom-template.yml \
  -f ~/templates/iot/home/ \
  --recurse

Define environment references

Some templates include environment references that let you provide custom resource names. The influx apply command prompts you to provide a value for each environment reference in the template. You can also provide values for environment references by including an --env-ref flag with a key-value pair comprised of the environment reference key and the value to replace it.

influx apply -o example-org -f /path/to/template.yml \
  --env-ref=bucket-name-1=myBucket
  --env-ref=label-name-1=Label1 \
  --env-ref=label-name-2=Label2

Include a secret when installing a template

Some templates use secrets in queries. Secret values are not included in templates. To define secret values when installing a template, include the --secret flag with the secret key-value pair.

# Syntax
influx apply -o <INFLUX_ORG> -f <FILE_PATH> \
  --secret=<secret-key>=<secret-value>

# Examples
# Define a single secret when applying a template
influx apply -o example-org -f /path/to/template.yml \
  --secret=FOO=BAR

# Define multiple secrets when applying a template
influx apply -o example-org -f /path/to/template.yml \
  --secret=FOO=bar \
  --secret=BAZ=quz

To add a secret after applying a template, see Add secrets.


Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

InfluxDB Cloud powered by TSM