Documentation

Use InfluxQL for diagnostics

The commands below are useful when diagnosing issues with InfluxDB Enterprise clusters. Use the influx CLI to run these commands.

SHOW STATS

To see node statistics, run SHOW STATS. The statistics returned by SHOW STATS are stored in memory only, and are reset to zero when the node is restarted.

For details on this command, see SHOW STATS.

SHOW DIAGNOSTICS

To see node diagnostic information, run SHOW DIAGNOSTICS. This returns information such as build information, uptime, hostname, server configuration, memory usage, and Go runtime diagnostics.

For details on this command, see SHOW DIAGNOSTICS.


Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 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