Global – October 30, 2026 -- An MQTT topic convention that works in a pilot can become unmanageable after a second plant, a new equipment vendor or the first external integration, according to new TDengine guidance. Inconsistent paths make subscriptions overbroad, access rules hard to review and equipment identity ambiguous downstream.

Global – October 30, 2026 -- Industrial architecture teams choosing between Sparkplug B and plain MQTT are really comparing the cost of maintaining a custom application contract with the cost of adopting and operating a shared one. Sparkplug B defines industrial conventions on top of MQTT. It does not replace MQTT or turn a broker into a historian.

Global – October 29, 2026 -- Historians that stamp MQTT messages with broker arrival time can display an old pressure reading as a new process condition, distorting aggregates, alarms and event order during outage replays.

Plain MQTT defines no process-time field

MQTT specifies only the transport of an application message. It prescribes no timestamp field, industrial clock model or time semantics. The publisher's application contract decides whether a payload carries a time, in what format and with what quality.

Global – October 28, 2026 -- An MQTT connection can recover while the historian still has a permanent data gap, because reconnection says nothing about where each measurement was durably held during the outage. Store and forward lowers that risk by retaining data near the failure point and replaying it after recovery, but it cannot restore a measurement that was never collected or never persisted at any boundary.

Global – October 28, 2026 -- Secure MQTT telemetry collection across IT/OT boundaries depends on the architecture around the broker, clients, identity and operations, not on choosing an encrypted port, according to TDengine guidance on industrial data ingestion.

Global – October 27, 2026 -- QoS 1 is the practical starting point for most industrial telemetry over MQTT, but none of the three QoS levels guarantees a complete historian, according to engineering guidance tied to the OASIS MQTT 5.0 standard.

Global – October 27, 2026 -- Neither MQTT retained messages nor persistent sessions can guarantee complete production history, so industrial operators who need every measurement must add application-level buffering and a historian, according to an engineering analysis of the OASIS MQTT 5.0 specification.

Global – October 27, 2026 -- Industrial teams can locate missing historian records by tracing one test message across five boundaries: broker receipt, subscriber receipt, parsing, database write and query. The approach comes from troubleshooting guidance on TDengine's MQTT ingestion, which warns that a live broker feed or a connected publisher proves only part of the chain.

Global – October 27, 2026 -- Even QoS 2's exactly-once delivery covers only one MQTT sender-receiver flow, not the subscriber's database transaction, so an MQTT broker cannot serve as an industrial historian. A broker moves messages between publishers and subscribers. A historian keeps time-indexed records that engineers can query, trend and aggregate later.

Global – October 27, 2026 -- An MQTT message is only a topic plus a payload, so a usable historian record needs four additions: stable equipment identity, typed measurements, a trustworthy timestamp and a schema that survives device and site growth. Engineers should settle these before configuring ingestion into TDengine TSDB Enterprise. Skipping that step can produce technically successful writes that create tables that are hard to query, compare or maintain.