What’s New in HiveMQ 4.11?

The HiveMQ Team is proud to announce the release of the HiveMQ Enterprise MQTT Platform 4.11. This release introduces the HiveMQ Enterprise Extension for Amazon Kinesis, enhanced supportability, and improved administrative visibility.

Highlights

• Added flexibility to ingest IoT data from MQTT clients into AWS with the general availability of the Enterprise Extension for Amazon Kinesis.
• New Diagnostic Archive function that automates the collection of information needed to debug performance-related issues in a HiveMQ cluster quickly.
• Expanded HiveMQ Control Center License view for increased transparency and ease of administration.

Additional IoT data ingestion with Amazon Kinesis Extension

HiveMQ’s integration capabilities are constantly evolving. This release adds more flexibility to create and support multi-cloud IoT architectures with the addition of the HiveMQ Enterprise Extension for Amazon Kinesis.

Amazon Kinesis is a suite of fully-managed Amazon Web Services (AWS) designed to ingest, process, and analyze data streams. Amazon Kinesis Data Streams can capture data from various sources as part of the Kinesis suite.

The HiveMQ Enterprise Extension for Amazon Kinesis lets you transfer MQTT data quickly and efficiently from your HiveMQ broker to Amazon Kinesis Data Streams.

Note: HiveMQ 4.11 moves the HiveMQ Enterprise Extension for Amazon Kinesis from early access preview into general availability.

How it works

The current release of our extension for Amazon Kinesis supports unidirectional messages flowing from MQTT clients via the HiveMQ broker to Amazon Kinesis Data Streams. The extension can be configured flexibly to forward messages to one or more Kinesis data streams. The extension is built for high message throughput, and configuration options are available to forward the original MQTT topic.

How it helps

In addition to the HiveMQ Enterprise Extension for Kafka, our new Kinesis extension gives you another way to integrate MQTT data into AWS.

Once your MQTT data is stored in Amazon Kinesis Data Streams, the data is available for processing with other AWS services. For example, the data can be streamed to any AWS data storage service with the Kinesis Data Analytics service.

HiveMQ Diagnostic Archive

If you experience problems with a HiveMQ cluster, our support engineers can provide immediate help. At such times, access to all relevant information is essential for accurate debugging and troubleshooting. Our newly introduced Diagnostic Archive feature streamlines the information-gathering process.

How it works

The HiveMQ Control Center now provides a fully automated process to capture all relevant information. Each HiveMQ broker node generates a ZIP file with the requested information when you initiate the collection process from your control center. When the process is complete, an individual diagnostic archive is stored on each broker node and can be uploaded to the HiveMQ support portal for further inspection.

Example diagnostic archive ZIP file:

How it helps

If your HiveMQ cluster experiences problems that require immediate attention, quick access to all pertinent information helps ensure the shortest possible MTTR (mean time to recovery). The Diagnostic Archive feature lets you easily collect all information that HiveMQ support engineers need to identify root causes and propose solutions.

HiveMQ Control Center License View

The License view in the HiveMQ Control Center now provides detailed information about the active HiveMQ license. The License view gives you a clear picture of current usages such as client connections and CPUs. All enabled features of the active license are also presented for additional transparency.

Example HiveMQ Control Center License view:

Other Noteworthy Fixes and Improvements

HiveMQ

• Improved stability and performance for inbound PUBLISH packets to high-volume shared subscriptions.
• Optimized memory consumption when millions of clients are connected.
• Fixed an issue that could cause a delay in metrics when millions of clients are connected.
• Improved metric reporting for nodes with millions of connected clients.
• Fixed an issue to prevent a potential memory leak on systems where no extension sets plugin initializers.

HiveMQ Swarm

• Improved user feedback when an incomplete HiveMQ Swarm REST API configuration is detected.