influx remote create
Replication remotes and replication streams can only be configured for InfluxDB OSS.
The influx remote create command creates a new remote InfluxDB connection for replicating data.
Usage
1. influx remote create [command options] [arguments...]
Flags
| Flag | Description | Input type | Maps to ? | |
|---|---|---|---|---|
—org-id |
Organization ID | string | INFLUX_ORG_ID |
|
-o |
—org |
Organization name | string | INFLUX_ORG |
-n |
—name |
Remote connection name | string | |
-d |
—description |
Remote connection description | string | |
—remote-url |
Remote InfluxDB instance URL | string | ||
—remote-api-token |
Remote InfluxDB API token | string | ||
—remote-org-id |
Remote InfluxDB organization ID | string | ||
—allow-insecure-tls |
Allows insecure TLS (self-signed certificates) | |||
—host |
InfluxDB HTTP address (default http://localhost:8086) |
string | INFLUX_HOST |
|
—skip-verify |
Skip TLS certificate verification | INFLUX_SKIP_VERIFY |
||
—configs-path |
Path to influx CLI configurations (default ~/.influxdbv2/configs) |
string | INFLUX_CONFIGS_PATH |
|
-c |
—active-config |
CLI configuration to use for command | string | |
—http-debug |
Inspect communication with InfluxDB servers | string | ||
—json |
Output data as JSON (default false) |
INFLUX_OUTPUT_JSON |
||
—hide-headers |
Hide table headers (default false) |
INFLUX_HIDE_HEADERS |
||
-t |
—token |
InfluxDB 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, --orgor--org-id: InfluxDB organization name or ID-t, --token: InfluxDB API token
Create a new remote with InfluxDB Cloud
1. influx remote create \
2. --name myremote \
3. --org-id <OSS org ID> \
4. --token <OSS token> \
5. --remote-url <remote URL> \
6. --remote-api-token <remote token> \
7. --remote-org-id <remote ord ID>
