Documentation

chronoctl migrate

The migrate command lets you migrate your Chronograf configuration store.

By default, Chronograf is delivered with BoltDB as a data store. For information on migrating from BoltDB to an etcd cluster as a data store, see Migrating to a Chronograf HA configuration.

Usage

chronoctl migrate [flags]

Flags

Flag Description Input type
-f --from Full path to BoltDB file or etcd (e.g. bolt:///path/to/chronograf-v1.db or etcd://user:pass@localhost:2379 (default: chronograf-v1.db) string
-t --to Full path to BoltDB file or etcd (e.g. bolt:///path/to/chronograf-v1.db or etcd://user:pass@localhost:2379 (default: etcd://localhost:2379) string

Provide etcd authentication credentials

If authentication is enabled on etcd, use the standard URI basic authentication format to define a username and password. For example:

etcd://username:password@localhost:2379

Provide etcd TLS credentials

If TLS is enabled on etcd, provide your TLS certificate credentials using the following query parameters in your etcd URL:

  • cert: Path to client certificate file or PEM file
  • key: Path to client key file
  • ca: Path to trusted CA certificates
etcd://127.0.0.1:2379?cert=/tmp/client.crt&key=/tst/client.key&ca=/tst/ca.crt

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: