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

FlagDescriptionInput type
-f--fromFull 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--toFull 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!


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

InfluxDB 3 Open Source Now in Public Alpha

InfluxDB 3 Open Source is now available for alpha testing, licensed under MIT or Apache 2 licensing.

We are releasing two products as part of the alpha.

InfluxDB 3 Core, is our new open source product. It is a recent-data engine for time series and event data. InfluxDB 3 Enterprise is a commercial version that builds on Core’s foundation, adding historical query capability, read replicas, high availability, scalability, and fine-grained security.

For more information on how to get started, check out: