Documentation

End-of-Life of Native Collector - MQTT

InfluxData has made a strategic decision to end-of-life (EOL) the Native Collector - MQTT feature that is currently available in InfluxDB Cloud (TSM). This EOL will take effect April 30th, 2024, after which this feature will be completely removed from InfluxDB Cloud (TSM) and will no longer be supported.

Please refer to the FAQ below for more details and guidance on alternate solutions currently available.

What is the Native Collector - MQTT Feature?

The Native Collector - MQTT feature was introduced in InfluxDB Cloud in 2022 as a way to ingest data directly from MQTT sources into InfluxDB Cloud. This feature has been removed and is no longer available to new customers or existing customers who have not been using it. It was only available to a limited number of existing customers who were actively using it.

Why is this feature being EOL’d?

The adoption of this feature was lower than anticipated given most customers continued to use Telegraf, InfluxData’s data collection agent, which provides more features for MQTT ingestion than this feature did. After a thorough assessment, we determined that our customers can have a similar (and even superior) experience using the MQTT Consumer Telegraf input plugin.

What alternatives are available in light of this EOL announcement?

We recommend using Telegraf with the MQTT Consumer Telegraf input plugin as an alternative to the Native Collector - MQTT feature.

Telegraf is InfluxData’s popular open source data collection agent that comes with 300+ plugins for data input and output, including MQTT.

What are the expected next steps?

The Native Collector - MQTT feature will continue to work and function until April 30th, 2024. In the meantime, we won’t release any new enhancements to the feature. After the EOL date, we will decommission the feature, and any MQTT subscriptions that you have will no longer receive and ingest data into InfluxDB.

Will I lose any data already ingested?

No, data already written to InfluxDB will not be affected by this change.

Where can I get more information on using Telegraf as a replacement for Native Collector - MQTT?

See MQTT Consumer Telegraf input plugin.


Was this page helpful?

Thank you for your feedback!


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

InfluxDB Cloud powered by TSM