I am excited today to announce that Tulip is actively rolling out support for MQTT as a Machine Data Source. This functionality will be rolling out to all customers over the next few releases, and will be available in LTS11.
Connect directly to your broker, ingest topics, extract values from complex payloads and more! Here is a quick demo video I threw together showing off the functionality -
Knowledge Base documentation for this new MQTT functionality is available here:
You are correct, if using OPCH, you will need to use the LTS11 image, which should be released in Mid-October.
We rolled out MQTT to a small subset of the customer base (a combination of tons of internal instances, trials, and a few select customers who were interested in playing with it) in r261, but in r262 we will roll this out to all other (non-LTS) customers. So far, we are yet to run into any show-stopping bugs, but that would be the key thing that could push back this date by a release or two.
If you are interested in testing in r261 and don’t yet have access shoot me an email at pete(dot)hartnett(at)tulip.co and I can enable this flag for you.
Hi @Pete_Hartnett , we are running on release r262 (Europe datacenter) but I cannot see the option for MQTT when setting up a new data source.
Only OPC UA is available.
Neither the On Prem Connector host is available, which will be needed for our use case.
When can we expect to get MQTT as a Machine Data Source implemented?
MQTT Initially was just enabled for a subset of customers, but with r263 (scheduled to go out early next week) this will be enabled for all customers. If you would like, I can enabled it now on your instance.
If all concludes well, LTS11 should be available later this week. Your pull is failing for the same reason, we just haven’t yet released the lts11 tagged version of OPCH.
Yes - We only release the OPCH for each LTS release, but MQTT has been available since r263 for standard release (just would need to use cloud connector host).
