content/influxdb3/cloud-serverless/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 Serverless.
{{< 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 %}} region URL
https://{{< influxdb/host >}}
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
{{< img-hd src="/img/chronograf/v1-influxdb3/cloud-serverless-connection.png" alt="Chronograf InfluxDB Cloud Serverless 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 also configure the connection when starting Chronograf:
Replace the following:
API_TOKEN{{% /code-placeholder-key %}}: API token with read permissions on the bucketBUCKET_NAME{{% /code-placeholder-key %}}: Bucket namechronograf --influxdb-v3-support-enabled \
--influxdb-type=influx-v3-serverless \
--influxdb-url=https://{{< influxdb/host >}} \
--influxdb-token=API_TOKEN \
--influxdb-default-db=BUCKET_NAME
For a complete list of configuration options, see InfluxDB 3 connection options.
[!Note]
DBRPs map to InfluxDB buckets
In {{% product-name %}}, database and retention-policy (DBRP) combinations are mapped to buckets using the
database-name/retention-policynaming 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
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.
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 %}} bucket, functionality in the {{< icon "crown" >}} InfluxDB Admin section of Chronograf is disabled.
To complete administrative tasks, use the following:
Annotations and dashboard variables work with {{% product-name %}} 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.