As requested in https://github.com/rabbitmq/rabbitmq-server/discussions/6331#discussioncomment-5796154 include all infos that were emitted in the MQTT connection created event also in the MQTT connection closed event. This ensures infos such as MQTT client ID are part of the connection closed event. Therefore, it's easy for the user to correlate between the two event types. Note that the MQTT plugin emits connection created and connection closed events only if the CONNECT packet was successfully processed, i.e.authentication was successful. Remove the disconnected_at property because it was never used. rabbit_event already adds a timestamp to any event. |
||
---|---|---|
.. | ||
include | ||
priv/schema | ||
src | ||
test | ||
.gitignore | ||
BUILD.bazel | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
LICENSE | ||
LICENSE-MPL-RabbitMQ | ||
Makefile | ||
README.md | ||
app.bzl |
README.md
RabbitMQ MQTT Plugin
Getting Started
This is an MQTT plugin for RabbitMQ.
The plugin is included in the RabbitMQ distribution. To enable it, use rabbitmq-plugins:
rabbitmq-plugins enable rabbitmq_mqtt
Default port used by the plugin is 1883
.
Documentation
MQTT plugin documentation is available from rabbitmq.com.
Contributing
See CONTRIBUTING.md.
Running Tests
After cloning RabbitMQ umbrella repository, change into the rabbitmq-mqtt
directory
and run
make tests
This will bring up a RabbitMQ node with the plugin enabled and run integration tests
against it. Note that there must be no other MQTT server running on ports 1883
and 8883
.
Copyright and License
(c) 2007-2020 VMware, Inc. or its affiliates.
Released under the Mozilla Public License, the same as RabbitMQ.