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 Cloud Serverless.

Prerequisites

Enable InfluxDB 3 support

To connect Chronograf to InfluxDB Cloud Serverless, 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 Cloud Serverless.

    Chronograf Server Type dropdown
  4. Enter your InfluxDB Cloud Serverless connection credentials:

    • Connection URL: InfluxDB Cloud Serverless region URL

      https://cloud2.influxdata.com
    • Connection Name: Name to uniquely identify this connection configuration

    • Database Token: InfluxDB API token with read permissions on the bucket you want to query

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

    • Unsafe SSL: Enable to skip SSL certificate verification for self-signed certificates

    Chronograf InfluxDB Cloud Serverless 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:

  • API_TOKEN: API token with read permissions on the bucket
  • BUCKET_NAME: Bucket name
chronograf --influxdb-v3-support-enabled \
  --influxdb-type=influx-v3-serverless \
  --influxdb-url=https://cloud2.influxdata.com \
  --influxdb-token=
API_TOKEN
\
--influxdb-default-db=
BUCKET_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.

DBRPs map to InfluxDB buckets

In InfluxDB Cloud Serverless, database and retention-policy (DBRP) combinations are mapped to buckets using the database-name/retention-policy naming convention or using manually created DBRP mappings. DBRP mappings are required to query InfluxDB Cloud using InfluxQL.

For information, see Create DBRP mappings.

You can 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 read-only

When connected to InfluxDB Cloud Serverless, the database view in Chronograf is read-only.

No administrative functionality

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

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

When connected to an InfluxDB Cloud Serverless bucket, functionality in the InfluxDB Admin section of Chronograf is disabled.

To complete administrative tasks, use the following:

Annotations and variables

Annotations and dashboard variables work with InfluxDB Cloud Serverless when a chronograf bucket exists and is accessible with the same API 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.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

InfluxDB Cloud Serverless