Documentation

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.

Note: 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. To specify a relative path to the BoltDB file, the prefix cannot be used.)

      $ chronoctl migrate -f bolt:///path/to/chronograf-v1.db -t etcd://localhost:2379
    

    Note: If you have authentication on etcd, use the standard URI format to define a username and password. For example, etcd://user:pass@localhost:2379

  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!


Linux Package Signing Key Rotation

All signed InfluxData Linux packages have been resigned with an updated key. If using Linux, you may need to update your package configuration to continue to download and verify InfluxData software packages.

For more information, see the Linux Package Signing Key Rotation blog post.

State of the InfluxDB Cloud (IOx) documentation

The new documentation for InfluxDB Cloud backed by InfluxDB IOx is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.