7.5 KiB
| title | seotitle | description | list_title | weight | menu | aliases | alt_links | related | metadata | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Use Chronograf to visualize data | Use Chronograf with InfluxDB Clustered | Chronograf is a data visualization and dashboarding tool designed to visualize data in InfluxDB 1.x. Learn how to use Chronograf with InfluxDB Clustered. | Chronograf | 201 |
|
|
|
|
|
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 %}}.
Prerequisites
- Download and install Chronograf
- An {{% product-name %}} cluster with:
- A database to query
- A database token with read permissions
Enable InfluxDB 3 support
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 >}}
Create an InfluxDB connection
-
Open Chronograf and click Configuration (wrench icon) in the navigation menu.
-
Click Add Connection.
-
In the Server Type dropdown, select InfluxDB Clustered.
-
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
-
Management Token: (Optional) A management token for administrative operations
-
Database Token: InfluxDB database token with read permissions on the database you want to query
-
Default Database: (Optional) Default database to use. When set, Chronograf limits queries to this database.
-
Telegraf Database Name: InfluxDB database 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/clustered-connection.png" alt="Chronograf InfluxDB Clustered 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.
Configure connection via CLI
You can also configure the connection when starting Chronograf:
Replace the following:
- {{% code-placeholder-key %}}
DATABASE_NAME{{% /code-placeholder-key %}}: Database name - {{% code-placeholder-key %}}
DATABASE_TOKEN{{% /code-placeholder-key %}}: Database token with read permissions - {{% code-placeholder-key %}}
MANAGEMENT_TOKEN{{% /code-placeholder-key %}}: Management token
chronograf --influxdb-v3-support-enabled \
--influxdb-type=influx-v3-clustered \
--influxdb-url=https://{{< influxdb/host >}} \
--influxdb-token=DATABASE_TOKEN \
--influxdb-mgmt-token=MANAGEMENT_TOKEN \
--influxdb-default-db=DATABASE_NAME
For a complete list of configuration options, see InfluxDB 3 connection options.
Query data in the Data Explorer
- In Chronograf, click {{< icon "graph" "v2" >}} Explore in the left navigation bar.
- Build and submit InfluxQL queries.
[!Note]
Schema information in the Data Explorer
{{% product-name %}} 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
FROMclause. 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.
[!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:SELECT * FROM mydb.autogen.measurement
Important notes
Database view is read-only
When connected to {{% product-name %}}, the database view in Chronograf is read-only.
No administrative functionality
Chronograf cannot be used for administrative tasks in {{% product-name %}}. For example, you cannot do the following:
- Define databases
- Modify retention policies
- Add users
- Kill queries
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 variables
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.
