Documentation

Install Chronograf

This page describes how to download and install Chronograf.

Content

TICK overview

Chronograf is the user interface for InfluxData’s TICK stack.

Download and install

The latest Chronograf builds are available on InfluxData’s Downloads page.

  1. On the Downloads page, scroll to the bottom and click Are you interested in InfluxDB 1.x Open Source? to expand the 1.x options. Scroll to the Chronograf section and select your desired Chronograf version and operating system. Execute the provided download commands.

    If your download includes a TAR package, save the underlying datastore chronograf-v1.db in directory outside of where you start Chronograf. This preserves and references your existing datastore, including configurations and dashboards, when you download future versions.

  2. Install Chronograf, replacing <version#> with the appropriate version:

    tar zxvf chronograf-1.11.1_darwin_amd64.tar.gz
    sudo dpkg -i chronograf_1.11.1_amd64.deb
    sudo yum localinstall chronograf-1.11.1.x86_64.rpm
  3. Start Chronograf:

    chronograf

Connect Chronograf to your InfluxDB instance or InfluxDB Enterprise cluster

  1. In a browser, navigate to localhost:8888.
  2. Provide the following details:
    • Connection String: InfluxDB hostname or IP, and port (default port is 8086).

    • Connection Name: Connection name.

    • Username and Password: If you’ve enabled InfluxDB authentication, provide your InfluxDB username and password. Otherwise, leave blank.

      To ensure distinct permissions can be applied, Chronograf user accounts and credentials should be different than InfluxDB credentials. For example, you may want to set up Chronograf to run as a service account with read-only permissions to InfluxDB. For more information, see how to manage InfluxDB users in Chronograf and manage Chronograf users.

    • Telegraf Database Name: (Optional) Telegraf database name. Default name is telegraf.

  3. Click Add Source.

Connect Chronograf to Kapacitor

  1. In Chronograf, click the configuration (wrench) icon in the sidebar menu, then select Add Config in the Active Kapacitator column.
  2. In the Kapacitor URL field, enter the hostname or IP of the machine that Kapacitor is running on. Be sure to include Kapacitor’s default port: 9092.
  3. Enter a name for your connection.
  4. Leave the Username and Password fields blank unless you’ve specifically enabled authorization in Kapacitor.
  5. Click Connect.

Note: Using Kapacitor is optional and not required to use Chronograf.


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