MQTT Message Log Extension
Logging Extension
Purpose: Logging
Version: 1.0.1    |   License: Apache V2
Provider: HiveMQ    |   Verified: yes


Purpose

The HiveMQ MQTT Message Log Extension is a very useful HiveMQ Extension for debugging and development purposes. It provides the possibility to follow up on any clients communicating with the broker on the terminal.

The extension logs the following events:

Prerequisites

Installation

  1. Download HiveMQ Mqtt Message Log Extension
  2. Move the file: “hivemq-mqtt-message-log-extension-1.0.1.zip” to the directory: “HIVEMQ_HOME/extensions”
  3. Unzip the file.
  4. Start HiveMQ.

Configuration

It is possible to opt out of specific log event types by adding a mqttMessageLog.properties files to your /hivemq-mqtt-message-log-extension folder. There is an example file available which removes the logging of publish messages. Just rename it to mqttMessageLog.properties

If you set verbose to true, all MQTT messages are logged with all the information available. Otherwise only basic information like client id, topic, qos and payload will be logged. See examples.

This properties file could have the following entries:


Note: use verbose=true very carefully as it will flood your log immediately.


Missing entries default to true. verbose defaults to false.

First Steps

Connect with an MQTT client of your choice. You should see a log message with its identifier, MQTT version, and all other connect options.

Examples

Verbose CONNECT message

“17:26:23.602 INFO - Received CONNECT from client ‘clientid’: Protocol version: ‘V_5’, Clean Start: ‘false’, Session Expiry Interval: ‘10000’, Keep Alive: ‘20000’, Maximum Packet Size: ‘40000’, Receive Maximum: ‘30000’, Topic Alias Maximum: ‘50000’, Request Problem Information: ‘true’, Request Response Information: ‘false’, Username: ‘the username’, Password: ‘the password’, Auth Method: ‘auth method’, Auth Data (Base64): ‘YXV0aCBkYXRh’, User Properties: [Name: ‘name0’, Value: ‘value0’], [Name: ‘name1’, Value: ‘value1’], Will: { Topic: ‘willtopic’, Payload: ‘payload’, QoS: ‘1’, Retained: ‘false’, Message Expiry Interval: ‘1234’, Duplicate Delivery: ‘false’, Correlation Data: ‘data’, Response Topic: ‘response topic’, Content Type: ‘content type’, Payload Format Indicator: ‘UTF_8’, Subscription Identifiers: ‘[1, 2, 3, 4]‘, User Properties: [Name: ‘name0’, Value: ‘value0’], [Name: ‘name1’, Value: ‘value1’], [Name: ‘name2’, Value: ‘value2’], Will Delay: ‘100’ }”

Basic CONNECT message

“17:26:23.602 INFO - Received CONNECT from client ‘clientid’: Protocol version: ‘V_5’, Clean Start: ‘false’, Session Expiry Interval: ‘10000’”

Need help?

If you encounter any problems, we are happy to help. The best place to get in contact is our support.



Back to marketplace