Announcing: Native MQTT Integration with HiveMQ and InfluxDB Cloud

| © Copyright 2022, InﬂuxData
Native MQTT
Integration
HiveMQ MQTT Broker and InﬂuxDB Cloud

Introductions
Gary Fowler
Product
Manager at
Inﬂux Data
Kudzai Manditereza
Developer Advocate
at HiveMQ, Founder
at Industry40.tv

Agenda
3
● Introduction to InﬂuxData & HiveMQ
● What is this new feature?
● See it in Action
○ Conﬁguring Subscription
○ Setting Up Parsing Rules
○ Visualizing Data
● Q&A

4
InﬂuxData is where developers build IoT,
real-time analytics and cloud applications

At a glance
5
FOUNDED
FOCUS
DIFFERENCE
OSS FOUNDATION
BUSINESS MODEL
2013
San Francisco HQ, 265 FTE’s, 99+ in technical functions
Where developers build real-time applications
One platform; one API across Multiple Clouds and On-Prem
Ingest, query, story using common tools regardless of architecture
1300+ Customers and 705,000 daily active OSS deployments;
Google , Cisco, SAP, Comcast, Tesla, Siemens, PTC, Honeywell, JP Morgan Chase
PLG Driven Usage and Subscription Model
Pay for what you use; Pay how you want. Credit card, cloud provider, annual contract
for IoT, Analytics and Cloud native services

Founded in 2012, based outside of Munich
HiveMQ helps move data to and from connected devices in an
eﬃcient, fast and reliable manner
130+ customers with production IoT applications

Native Collection
7
The ability to directly ingest data from popular
data sources without the need to do any
transformation to Line Protocol or run a
Telegraf agent

Multiple InfluxDB Ingestion Options
8
Available for many popular
development languages:
Make API Calls to write
data to InfluxDB Cloud
Offers over 200 Plug-Ins
to collect data from many
data sources
Interfaces directly with
Cloud Data Sources (in
this case, MQTT Brokers)
Client Libraries Telegraf Agent Native Collection

Telegraf & Client Libraries - Great Options
9
Cloud First
Lack of Available
Resources
Quick PoC or
Adoption
Cloud First Companies don’t always have a location/place to install the Telegraf
Agent and want a serverless solution where their data stays in the cloud
Sometimes, you want to do a lightning evaluation, PoC, or even adoption and
don’t have time to write any code or install any software
Often, development resources are already building other important products &
solutions for their company
Except in certain situations:

MQTT Topic Subscriptions
10
With this new feature, InﬂuxDB customers can
subscribe to topics being published by their
own devices and sent through a message
broker directly to the InﬂuxDB Cloud service;
without writing any code or installing any
additional software

MQTT Ingestion Comparison

Integration with an MQTT Broker
12
Today, we are going to show you how easy it is
to use this new feature to start subscribing to
MQTT topics to ingest data into InﬂuxDB Cloud
where you can immediately start visualizing,
analyzing, and transforming

13
For today’s demonstration, we are going to
conﬁgure InﬂuxDB cloud to subscribe to topics
from a HiveMQ MQTT Broker

Demo
HiveMQ MQTT Broker and MQTT Publishing

Use Case - Remote Asset Monitoring

Demo Use Case
16
2 IoT Devices
publishing MQTT
Data, reporting:
◆ Temperature
◆ Humidity
HiveMQ MQTT
Broker installed on
AWS
InﬂuxDB Cloud to
Visualize, Monitor, &
Alert on that Data
IoT Devices HiveMQ MQTT Broker InﬂuxDB Cloud

Simple 3 Step Configuration
17
Define Parsing Rules
● Configure Rules for
finding timestamps,
measurements, tags, and
field information in the
MQTT messages
Configure Broker
● Broker URL
● Broker TCP/IP Port
Number
● Broker Authentication
Type
● Broker Authentication
Parameters
Configure Topic
● Topic Name
● InfluxDB Bucket

Switch to Demo
Show Setting up the Broker connection and topic subscription
Switch back to slides to discuss parsing rules

Setting up Parsing Rules
19
Parsing Rules allow you to find the data in the
MQTT messages that you want to be elements
within InfluxDB (timestamps, measurements,
tags, and fields)

Parsing Rules - Supported Formats
20
If MQTT Messages are
already in Line Protocol
format, then no additional
configuration necessary
If MQTT Messages are
in JSON format, then
you use JSON path
names to identify JSON
key/value pairs to use
for InfluxDB elements
For messages in any
other format, you use
REGEX string
matching/grouping to
find and designate
InfluxDB elements
Line Protocol JSON String

JSON Example
21
{
"temperature":27,
"device_id":1002,
"time":1660242495828,
"device_type":"raspberry_pi",
"Error_state":"normal_operation",
"model_id":"RASPBERRY-PI-3B",
"humidity":64
}
Element
Field
TAG
Timestamp
Measurement
Field
Field
Field
Type
Float
Integer
String
String
String
Float
JSON Path
$.temperature
$.device_id
$.time
$.device_type
$.error_state
$.model_id
$.humidity

Demo
Conﬁguring JSON Parsing Rules & Visualizations/Alerts

Switch back to Demo
Show Setting up the parsing rules and completing the
subscription’
Show visualizing the data
Discuss ﬂux and being able to downsample and transform, etc.

Getting Started with HiveMQ Cloud
24

Getting Started with Native MQTT
25
Configure MQTT
● Configure your broker
details
● Configure your
subscription details
● Configure your parsing
rules
Sign-Up for Pay as You Go Cloud
Account
● If not already an InfluxDB
Cloud 2.0 customer,
sign-up for a free
account and then
upgrade to Pay-as-you-go
Create a Bucket
● After logging in, select
Load Data, Buckets and
create a new bucket

Enroll for free at inﬂuxdbu.com
Join InﬂuxDB University

Deeply technical,
single-track InfluxDB event
Join the two-day developer conference dedicated
to building IoT, analytics, and cloud applications
with InfluxDB.
November 2-3, 2022
Register today for free: influxdays.com

Cloud Native Subscriptions
Q&A
28

Screenshots

30

31

32

33

34

35

36

Announcing: Native MQTT Integration with HiveMQ and InfluxDB Cloud

More Related Content

What's hot

Similar to Announcing: Native MQTT Integration with HiveMQ and InfluxDB Cloud

More from InfluxData

Recently uploaded

Announcing: Native MQTT Integration with HiveMQ and InfluxDB Cloud