Documentation

Create a Chronograf HA configuration

To create a Chronograf high-availability (HA) configuration using an etcd cluster as a shared data store, do the following:

  1. Install and start etcd
  2. Set up a load balancer for Chronograf
  3. Start Chronograf

Have an existing Chronograf configuration store that you want to use with a Chronograf HA configuration? Learn how to migrate your Chrongraf configuration to a shared data store.

Architecture

UserUserUserUserLoad BalancerChronografChronografChronografetcd Cluster

Install and start etcd

  1. Download the latest etcd release from GitHub. (For detailed installation instructions specific to your operating system, see Install and deploy etcd.)
  2. Extract the etcd binary and place it in your system PATH.
  3. Start etcd.

Start Chronograf

Run the following command to start Chronograf using etcd as the storage layer. The syntax depends on whether you’re using command line flags or the ETCD_ENDPOINTS environment variable.

Define etcd endpoints with command line flags
# Syntax
chronograf --etcd-endpoints=<etcd-host>
# Examples

# Add a single etcd endpoint when starting Chronograf

chronograf --etcd-endpoints=localhost:2379

# Add multiple etcd endpoints when starting Chronograf
chronograf \
  --etcd-endpoints=localhost:2379 \
  --etcd-endpoints=192.168.1.61:2379 \
  --etcd-endpoints=192.192.168.1.100:2379
Define etcd endpoints with the ETCD_ENDPOINTS environment variable

# Provide etcd endpoints in a comma-separated list
export ETCD_ENDPOINTS=localhost:2379,192.168.1.61:2379,192.192.168.1.100:2379

# Start Chronograf
chronograf
Define etcd endpoints with TLS enabled

Use the --etcd-cert flag to specify the path to the etcd PEM-encoded public certificate file and the --etcd-key flag to specify the path to the private key associated with the etcd certificate.

chronograf --etcd-endpoints=localhost:2379 \
  --etcd-cert=path/to/etcd-certificate.pem \
  --etcd-key=path/to/etcd-private-key.key

For more information, see Chronograf etcd configuration options.


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.

InfluxDB Cloud backed by InfluxDB IOx

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by IOx, this is the correct documentation.

If powered by TSM, see the TSM-based InfluxDB Cloud documentation.

InfluxDB Cloud backed by InfluxDB TSM

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine which enables nearly unlimited series cardinality and SQL query support. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by TSM, this is the correct documentation.

If powered by IOx, see the IOx-based InfluxDB Cloud documentation.

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.