Documentation

Use Chronograf to visualize data

Chronograf is a data visualization and dashboarding tool designed to visualize data in InfluxDB 1.x using the InfluxQL query language. This page walks through how to use Chronograf with InfluxDB 3 Enterprise.

Prerequisites

Enable InfluxDB 3 support

To connect Chronograf to InfluxDB 3 Enterprise, start Chronograf with InfluxDB 3 support enabled using one of the following methods:

chronograf --influxdb-v3-support-enabled
export INFLUXDB_V3_SUPPORT_ENABLED=true
chronograf

Create an InfluxDB connection

  1. Open Chronograf and click Configuration (wrench icon) in the navigation menu.

  2. Click Add Connection.

    Chronograf connections landing page

  3. In the Server Type dropdown, select InfluxDB 3 Enterprise.

    Chronograf Server Type dropdown
  4. Enter your InfluxDB 3 Enterprise connection credentials:

    • Connection URL: URL of your InfluxDB 3 Enterprise cluster

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

    • Database Token: InfluxDB database token

      with read permissions on the database you want to query

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

    Chronograf InfluxDB 3 Enterprise connection configuration
  5. Click Add Connection.

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

  7. To configure a Kapacitor connection, provide the necessary credentials, and then click Continue. Otherwise, click Skip.

  8. Click Finish.

Configure connection via CLI

You can also configure the connection when starting Chronograf:

Replace the following:

chronograf --influxdb-v3-support-enabled \
  --influxdb-type=influx-v3-enterprise \
  --influxdb-url=http://localhost:8181 \
  --influxdb-token=
DATABASE_TOKEN
\
--influxdb-default-db=
DATABASE_NAME

For a complete list of configuration options, see InfluxDB 3 connection options.

Query data in the Data Explorer

  1. In Chronograf, click Explore in the left navigation bar.
  2. Build and submit InfluxQL queries.

Schema information in the Data Explorer

InfluxDB 3 Enterprise supports InfluxQL metaqueries, so schema information is available in the Data Explorer to help build queries. You can also use fully qualified measurements in the FROM clause. For example:

-- Fully qualified measurement
SELECT * FROM "db-name"."rp-name"."measurement-name"

-- Fully qualified measurement shorthand (use the default retention policy)
SELECT * FROM "db-name".."measurement-name"

For more information about available InfluxQL functionality, see InfluxQL feature support.

Important notes

Database view is disabled

When connected to InfluxDB 3 Enterprise, the database view in Chronograf is disabled.

No administrative functionality

Chronograf cannot be used for administrative tasks in InfluxDB 3 Enterprise. For example, you cannot do the following:

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

When connected to an InfluxDB 3 Enterprise database, functionality in the InfluxDB Admin section of Chronograf is disabled.

To complete administrative tasks, use the influxdb3 CLI.

Annotations and variables

Annotations and dashboard variables work with InfluxDB 3 Enterprise when a chronograf database exists and is accessible with the same database token.

When setting up variables with dynamic tag values, the backend query limits the scope of the record search with a time condition. By default, this is time > now() - 7d. Tags from records older than this limit are ignored. To change this setting, use the --influxdb-v3-time-condition flag or INFLUXDB_V3_TIME_CONDITION environment variable.


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