Documentation

InfluxDB Enterprise

Manage node labels

Assign user-defined labels to nodes in your InfluxDB Enterprise cluster. Node labels are user-defined key-value pairs assigned to nodes in your cluster that act as metadata for each node.

The tools used for viewing and managing node labels in your InfluxDB Enterprise cluster are the influxd-ctl show command and the influxd-ctl node-label command and subcommands.

View node labels

Use the influxd-ctl show command to view information about nodes in your InfluxDB Enterprise cluster, including node labels.

influxd-ctl show

View example influxd-ctl show output

Add labels to a node

To add a label to a node in your InfluxDB Enterprise cluster, use the influxd-ctl node-labels set command and include the following flags:

  • -nodeid: Node ID to add the labels to
  • -labels: JSON object of label key-value pairs
influxd-ctl node-labels set -nodeid 4 -labels '{"az":"us-east","team":"amer"}'

View influxd-ctl show output with added labels

Update node labels

To update node labels, use the influxd-ctl node-labels set command and include the following flags:

  • -nodeid: Node ID to update the labels on
  • -labels: JSON object of label key-value pairs to update
influxd-ctl node-labels set -nodeid 4 -labels '{"team":"emea"}'

Only label keys included in the -labels JSON object are updated. All other node labels are not modified.

View influxd-ctl show output with updated labels

Delete node labels

To update node labels, use the influxd-ctl node-labels set command and include the following flags:

  • -nodeid: Node ID to update the labels on
  • -labels: JSON object of label key-value pairs to update
influxd-ctl node-labels delete -nodeid 4 -labels '["team"]'

View influxd-ctl show output with deleted label

Programmatically access node labels

Use the /show-cluster endpoint of meta node API to return a JSON object containing information about your InfluxDB Enterprise cluster, including node labels.

GET meta-node-host:8191/show-cluster

View example JSON output

Was this page helpful?

Thank you for your feedback!

© 2026 InfluxData, Inc.

Where are you running InfluxDB?

Customize your InfluxDB Enterprise URL and we’ll update code examples for you.

Default
Custom

For more information, see InfluxDB Enterprise HTTP settings.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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