influx stacks init

  • influx CLI 2.0.1+
  • InfluxDB 2.0.1+

The influx stacks init command initializes an InfluxDB stack.

Usage

1. influx stacks init [flags]

Flags

Flag Description Input type Maps to ?
-c —active-config CLI configuration to use for command string
—configs-path Path to influx CLI configurations (default ~/.influxdbv2/configs) string INFLUX_CONFIGS_PATH
-h —help Help for the init command
—hide-headers Hide table headers (default false) INFLUX_HIDE_HEADERS
—host HTTP address of InfluxDB (default http://localhost:8086) string INFLUX_HOST
—http-debug Inspect communication with InfluxDB servers. string
—json Output data as JSON (default false) INFLUX_OUTPUT_JSON
-o —org Organization name (mutually exclusive with —org-id) string INFLUX_ORG
—org-id Organization ID (mutually exclusive with —org) string INFLUX_ORG_ID
—skip-verify Skip TLS certificate verification INFLUX_SKIP_VERIFY
-d —stack-description Stack description string
-n —stack-name Stack name string
-u —template-url Template URLs to associate with a stack list of strings
-t —token API token string INFLUX_TOKEN

Examples

Authentication credentials

The examples below assume your InfluxDB host, organization, and token are provided by either the active influx CLI configuration or by environment variables (INFLUX_HOST, INFLUX_ORG, and INFLUX_TOKEN). If you do not have a CLI configuration set up or the environment variables set, include these required credentials for each command with the following flags:

  • --host: InfluxDB host
  • -o, --org or --org-id: InfluxDB organization name or ID
  • -t, --token: InfluxDB API token
Initialize a stack with a name and description
1. influx stacks init -n "Example Stack" -d "InfluxDB stack for monitoring some awesome stuff"
Initialize a stack with a name and URLs to associate with the stack
1. influx stacks init -n "Example Stack" -u https://example.com/template-1.yml

templates