HiveMQ integrates with InfluxDB

Overview

HiveMQ and InfluxDB form the messaging and persistence layers of the MING stack. HiveMQ collects data from distributed devices via MQTT, and InfluxDB stores that data as time-series for querying and analysis.

Integration architecture

The typical integration uses a middleware component (like Node-RED, Telegraf, or a custom application) to bridge HiveMQ and InfluxDB:

1. Devices publish MQTT messages to HiveMQ
2. Middleware subscribes to relevant topics
3. Middleware parses payloads and writes to InfluxDB via Line Protocol or HTTP API

Direct integration options

• Telegraf: InfluxData's agent includes an MQTT consumer input plugin that connects directly to HiveMQ
• HiveMQ Extension SDK: Build a custom extension to write directly to InfluxDB
• Node-RED: Visual flows to transform MQTT messages into InfluxDB writes

Schema considerations

• Use HiveMQ topic hierarchy to inform InfluxDB measurement and tag structure
• Consider payload format (JSON, Protobuf) and parsing overhead
• Batch writes to InfluxDB for high-throughput scenarios

Use cases

• Industrial monitoring: Sensor data collection and historical trending
• Predictive maintenance: Vibration and temperature data storage
• Energy management: Power consumption tracking and analytics