Documentation

Use Chronograf with InfluxDB OSS

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

API token hashing is enabled by default in InfluxDB OSS 2.9.0

Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.

For more information, see Token hashing.

Chronograf is a data visualization and dashboarding tool designed to visualize data in InfluxDB 1.x. It is part of the TICKstack that provides an InfluxQL data explorer, Kapacitor integrations, and more. Continue to use Chronograf with InfluxDB Cloud and InfluxDB OSS 2.9 and the 1.x compatibility API.

Create an InfluxDB connection

  1. In Chronograf, click Configuration in the left navigation bar, and then click Add Connection.

  2. Toggle the InfluxDB v2 Auth option at the bottom of the form. InfluxDB v2 Auth toggle

  3. Enter your InfluxDB connection credentials:

    • Connection URL: InfluxDB URL (see InfluxDB Cloud regions or InfluxDB OSS URLs)

      http://localhost:8086
    • Connection Name: Name to uniquely identify this connection configuration

    • Organization: InfluxDB organization

    • Token: InfluxDB API token

    • Telegraf Database Name: InfluxDB bucket Chronograf uses to populate parts of the application, including the Host List page (default is telegraf)

    • Default Retention Policy: default retention policy (leave blank)

      DBRPs map to InfluxDB buckets

      In InfluxDB 2.9, database/retention-policy (DBRP) combinations are mapped to buckets using the database-name/retention-policy naming convention. DBRP mappings are required to query InfluxDB 2.9 using InfluxQL.

      For information, see DBRP mapping.

  4. Click Add Connection.

  5. Select the dashboards you would like to create, and then click Next.

  6. To configure a Kapacitor connection, provide the necessary credentials, and then click Continue. Otherwise, click Skip. For information about using Kapacitor with InfluxDB Cloud or InfluxDB OSS 2.9, see Use Kapacitor with InfluxDB.

  7. Click Finish.

Important notes

Update upgraded InfluxDB connections

If using Chronograf with an InfluxDB instance that was upgraded from 1.x to 2.x, update your InfluxDB connection configuration in Chronograf to use the InfluxDB v2 Auth option and provide an organization and a token. Without an organization, Chronograf cannot use Flux to query InfluxDB.

No administrative functionality

Chronograf cannot be used for administrative tasks in InfluxDB Cloud and InfluxDB OSS 2.9. For example, you cannot do the following:

  • Define databases
  • Modify retention policies
  • Add users
  • Kill queries

When connected to an InfluxDB Cloud or InfluxDB 2.9 database, functionality in the InfluxDB Admin section of Chronograf is disabled.

To complete administrative tasks, use the following:

Limited InfluxQL support

InfluxDB Cloud and InfluxDB OSS 2.9 support InfluxQL read-only queries. For more information, see InfluxQL support.


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.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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