TDengine TSDB Enterprise

Global – October 29, 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.

Broker placement decides which systems need a route to OT

The broker can sit near sources, in an industrial DMZ or in another approved service zone, depending on the site's threat model, reliability needs and operating ownership. An IT subscriber should connect only to an approved broker endpoint, not to controllers or the wider OT network. The guidance cites NIST's Guide to Operational Technology Security, which requires OT designs to weigh performance, reliability and safety alongside cybersecurity risk.

Global – October 29, 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.

Four pipeline stages each own a separate loss boundary

An industrial MQTT path commonly runs through publisher, broker, collector and historian. A source-side buffer covers a site-to-broker interruption. A broker-side queue helps an offline subscriber receive messages the broker already accepted. A collector-side buffer covers messages after collection but before the historian confirms storage. None of these mechanisms automatically covers the others.

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.

Global – October 27, 2026 -- Industrial data architects should choose OPC UA when a collector must discover and read a structured source, and MQTT when producers publish through a broker to one or more consumers, according to a TDengine technical comparison. The guide adds that the two names do not describe equivalent layers, so the rule is only a starting point.

OPC UA preserves equipment context that MQTT leaves to the architect

OPC UA is a family of specifications covering Client/Server services, information modeling, Alarms and Conditions, Historical Access and PubSub. A server can organize measurements under equipment objects, attach engineering units and ranges, and expose status, timestamps and methods. A client can browse that address space instead of encoding meaning in topic strings.

Not every server delivers a rich model, however. Some expose flat tag lists, incomplete metadata or vendor-specific structures.

Global – October 27, 2026 -- A pump pressure trend shows when a value left its normal range but cannot show which alarm changed state, what severity the server reported, or when an operator acknowledged it. Those answers sit in separate OPC UA records, and historian designs must decide which questions each record has to answer.

Tag history stores values, not alarm lifecycles

An OPC UA client collects a variable through a monitored item. When DataChange criteria are met, the server sends a DataValue that the historian can store with source timestamp, server timestamp, and StatusCode, depending on the collector mapping. Sampling, deadbands, queues, and timestamp selection determine how much process behavior survives.