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!


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: