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!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2