Eclipse Hono abstracts telemetry ingestion from edge devices regardless of protocol. Once data flows through Hono, it can be directed to InfluxDB for time-series storage and analysis using Hono's northbound AMQP/Kafka APIs.
Integration Architecture
Devices connect to Hono via MQTT, CoAP, AMQP or HTTP
Hono forwards normalized telemetry messages over AMQP 1.0 or Kafka
A consumer application (e.g. a Spring Boot or Quarkus service) reads from Hono and writes to InfluxDB using the InfluxDB client library
Grafana visualizes the InfluxDB data
Use Cases
Industrial monitoring: sensor data from PLCs → Hono → InfluxDB → Grafana
Predictive maintenance: vibration and temperature telemetry normalized by Hono, stored in InfluxDB for anomaly detection
Energy management: smart-meter data ingested via CoAP or MQTT through Hono, persisted in InfluxDB
Getting Started
Deploy Hono with the desired protocol adapters
Register devices in Hono's device registry
Configure an AMQP or Kafka consumer application
Use the InfluxDB client to batch-write telemetry points
Set up retention policies and continuous queries in InfluxDB