Documentation

influx remote delete

Replication remotes and replication streams can only be configured for InfluxDB OSS.

The influx remote delete command delete an existing remote InfluxDB connection used for replication.

Usage

influx remote delete [command options] [arguments...]
  • Copy
  • Fill window

Flags

FlagDescriptionInput typeMaps to ?
-i--idRemote connection ID to delete
--hostInfluxDB HTTP address (default http://localhost:8086)stringINFLUX_HOST
--skip-verifySkip TLS certificate verificationINFLUX_SKIP_VERIFY
--configs-pathPath to influx CLI configurations (default ~/.influxdbv2/configs)stringINFLUX_CONFIGS_PATH
-c--active-configCLI configuration to use for commandstring
--http-debugInspect communication with InfluxDB serversstring
--jsonOutput data as JSON (default false)INFLUX_OUTPUT_JSON
--hide-headersHide table headers (default false)INFLUX_HIDE_HEADERS
-t--tokenInfluxDB API tokenstringINFLUX_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

Delete a remote

  1. Use influx remote list to get the ID for the remote you want to delete.
    $ influx remote list --org-id <OSS org ID> --token <OSS token>
    ID			        Name		Org ID
    0ooxX0xxXo0x 	    myremote    [...]
    
    • Copy
    • Fill window
  2. Use the following command to delete the remote:
    influx remote delete \
      --org-id <OSS org ID> \
      --token <OSS token> \
      --id 0ooxX0xxXo0x
    
    • Copy
    • Fill window

Was this page helpful?

Thank you for your feedback!


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.

Read more

New in InfluxDB 3.2

Key enhancements in InfluxDB 3.2 and the InfluxDB 3 Explorer UI is now generally available.

See the Blog Post

InfluxDB 3.2 is now available for both Core and Enterprise, bringing the general availability of InfluxDB 3 Explorer, a new UI that simplifies how you query, explore, and visualize data. On top of that, InfluxDB 3.2 includes a wide range of performance improvements, feature updates, and bug fixes including automated data retention and more.

For more information, check out:

InfluxDB Cloud powered by TSM