Migrate to a Chronograf HA configuration

Use chronoctl to migrate your Chronograf configuration store from BoltDB to a shared etcd data store used for Chronograf high-availability (HA) clusters.

Update resource IDs

Migrating Chronograf to a shared data source creates new source IDs for each resource. Update external links to Chronograf dashboards to reflect new source IDs.

  1. Stop the Chronograf server by killing the chronograf process.

  2. To prevent data loss, we strongly recommend that you back up your Chronograf data store before migrating to a Chronograf cluster.

  3. Install and start etcd.

  4. Run the following command, specifying the local BoltDB file and the etcd endpoint beginning with etcd://. (We recommend adding the prefix bolt:// to an absolute path. Do not use the prefix to specify a relative path to the BoltDB file.)

    chronoctl migrate \
      --from bolt:///path/to/chronograf-v1.db \
      --to etcd://localhost:2379
    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:

    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
  5. Update links to Chronograf (for example, from external sources) to reflect your new URLs:

    • from BoltDB: http://localhost:8888/sources/1/status
    • to etcd: http://localhost:8888/sources/373921399246786560/status
  6. Set up a load balancer for Chronograf.

  7. Start Chronograf.

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.

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: