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!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, 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