Use Chronograf with InfluxDB OSS

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

    • 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.7, 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.7 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.7, 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.7. 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.7 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.7 support InfluxQL read-only queries. For more information, see InfluxQL support.

Was this page helpful?

Thank you for your feedback!

Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.