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.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

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:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

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