Clarification on Supported OPC UA → MQTT Architecture (Managed Broker in CDF)

Question

Hi Cognite Team,We are currently defining an integration pattern for a partner who will provide data from an OPC UA source into Cognite Data Fusion.Our preference is to use a managed MQTT broker in CDF and avoid deploying any self-hosted MQTT broker or additional bridge components on-prem.Based on the documentation, we understand that the OPC UA Extractor supports an mqtt: output mode, but it also references a requirement for the MQTT-CDF Bridge and a configured broker host/port.To ensure we define the correct and supported architecture, could you please clarify:	Is it supported to configure the OPC UA Extractor to publish directly to the Cognite-hosted MQTT broker in CDF?			If using the Cognite-managed MQTT broker, is the MQTT-CDF Bridge still required?			Is a self-hosted MQTT broker mandatory when using the mqtt: configuration in the OPC UA Extractor?			What is the recommended architecture today for a partner delivering OPC UA data into CDF using MQTT?	Our intended target architecture is:OPC UA → Cognite OPC UA Extractor → Cognite Hosted MQTT Broker → CDFwithout deploying:	A self-hosted MQTT broker			The MQTT-CDF Bridge on-prem	We would appreciate confirmation of the supported and recommended approach for new integrations.

Einar Omang · Answer

The MQTT pushing feature in the OPC-UA extractor does not do what you think it does. It is deprecated and will be removed shortly, so it can unfortunately not be used in this way. It was built for a different use case a long time ago, but it hasn’t really been kept up to date.

If this is something you need, then it should be considered a feature request, and not something we currently support.

Sign up

Welcome to Cognite Hub

Scanning file for viruses.

This file cannot be downloaded