Documentation

Chronograf

Chronograf frequently asked questions (FAQs)

How do I connect Chronograf to an InfluxDB Enterprise cluster?

The connection details form requires additional information when connecting Chronograf to an InfluxDB Enterprise cluster.

When you enter the InfluxDB HTTP bind address in the Connection String input, Chronograf automatically checks if that InfluxDB instance is a data node. If it is a data node, Chronograf automatically adds the Meta Service Connection URL input to the connection details form. Enter the HTTP bind address of one of your cluster’s meta nodes into that input and Chronograf takes care of the rest.

Cluster connection details

Note that the example above assumes that you do not have authentication enabled. If you have authentication enabled, the form requires username and password information. For more details about monitoring an InfluxDB Enterprise cluster, see the Monitor an InfluxDB Enterprise Cluster guide.

Was this page helpful?

Thank you for your feedback!

© 2025 InfluxData, Inc.

Where are you running InfluxDB?

Select your InfluxDB Cloud region and cluster or your InfluxDB OSS URL and we’ll customize code examples for you. Identify your InfluxDB Cloud cluster.

  • InfluxDB Cloud
  • InfluxDB OSS or Enterprise
AWS

  • US West (Oregon)

GCP
Azure
Default
Custom

For more information, see InfluxDB Cloud regions or InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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