content/influxdb3/cloud-dedicated/process-data/visualize/chronograf.md
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 {{% product-name %}}.
To connect Chronograf to {{% product-name %}}, start Chronograf with InfluxDB 3 support enabled using one of the following methods:
{{< tabs-wrapper >}} {{% tabs %}} CLI flag Environment variable {{% /tabs %}} {{% tab-content %}}
chronograf --influxdb-v3-support-enabled
{{% /tab-content %}} {{% tab-content %}}
export INFLUXDB_V3_SUPPORT_ENABLED=true
chronograf
{{% /tab-content %}} {{< /tabs-wrapper >}}
Open Chronograf and click Configuration (wrench icon) in the navigation menu.
Click Add Connection.
{{< img-hd src="/img/chronograf/1-6-connection-landing-page.png" alt="Chronograf connections landing page" />}}
In the Server Type dropdown, select InfluxDB Cloud Dedicated.
{{< img-hd src="/img/chronograf/v1-influxdb3/server-type-dropdown.png" alt="Chronograf Server Type dropdown" />}}
Enter your {{% product-name %}} connection credentials:
Connection URL: {{% product-name omit=" Clustered" %}} cluster URL
https://{{< influxdb/host >}}
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)
To enable database management features, provide the following credentials:
influxctl configuration)influxctl configuration)You can configure the following optional database access fields:
{{< img-hd src="/img/chronograf/v1-influxdb3/cloud-dedicated-with-mgmt.png" alt="Chronograf InfluxDB Cloud Dedicated connection configuration" />}}
Click Add Connection.
Select the dashboards you would like to create, and then click Next.
To configure a Kapacitor connection, provide the necessary credentials, and then click Continue. Otherwise, click Skip.
Click Finish.
You can configure the connection when starting Chronograf.
Replace the following:
ACCOUNT_ID{{% /code-placeholder-key %}}: Account IDCLUSTER_ID{{% /code-placeholder-key %}}: Cluster IDDATABASE_NAME{{% /code-placeholder-key %}}: Database nameDATABASE_TOKEN{{% /code-placeholder-key %}}: Database token with read permissionsMANAGEMENT_TOKEN{{% /code-placeholder-key %}}: Management tokenchronograf --influxdb-v3-support-enabled \
--influxdb-type=influx-v3-cloud-dedicated \
--influxdb-url=https://{{< influxdb/host >}} \
--influxdb-token=DATABASE_TOKEN \
--influxdb-mgmt-token=MANAGEMENT_TOKEN \
--influxdb-cluster-id=CLUSTER_ID \
--influxdb-account-id=ACCOUNT_ID \
--influxdb-default-db=DATABASE_NAME \
--tags-csv-path=/path/to/tags
Replace the following:
DATABASE_NAME{{% /code-placeholder-key %}}: Database nameDATABASE_TOKEN{{% /code-placeholder-key %}}: Database token with read permissionschronograf --influxdb-v3-support-enabled \
--influxdb-type=influx-v3-cloud-dedicated \
--influxdb-url=https://{{< influxdb/host >}} \
--influxdb-token=DATABASE_TOKEN \
--influxdb-default-db=DATABASE_NAME
For a complete list of configuration options, see InfluxDB 3 connection options.
For {{% product-name %}}, you can predefine tags for the query builder and control filters using CSV files.
CSV file requirements:
mydb.csv for a database named mydb);) as field delimitersmeasurement;tag-key;tag-valueExample CSV content:
home;room;Living Room
home;room;cellar
home;room;attic
[!Note]
Schema information in the Data Explorer
When using Tags CSV files, the query builder uses the predefined tags. When a Default Database is set, the
SHOW DATABASESquery result is limited to that database.You can also use fully qualified measurements in the
FROMclause. For example:sql-- 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.
[!Note]
DBRPs map to InfluxDB databases
In {{% product-name %}}, databases and retention policies (DBRPs) are no longer separate entities in the data model. Rather than having one or more retention policies, an {{% product-name %}} database has a retention period that defines the maximum age of data to retain.
InfluxQL queries still use the 1.x DBRP convention, but queries are routed to databases using the
database-name/retention-policynaming pattern. For example, the following query routes to the {{% product-name %}} database namedmydb/autogen:sqlSELECT * FROM mydb.autogen.measurement
When connected to {{% product-name %}}, the database view in Chronograf is read-only.
Chronograf cannot be used for administrative tasks in {{% product-name %}}. For example, you cannot do the following:
When connected to an {{% product-name %}} database, functionality in the {{< icon "crown" >}} InfluxDB Admin section of Chronograf is disabled.
To complete administrative tasks, use the influxctl CLI.
Annotations and dashboard variables work with {{% product-name %}} 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.