MoquetteMon - Revision history

Ctreber at 12:56, 12 August 2017

2017-08-12T12:56:39Z

← Older revision		Revision as of 12:56, 12 August 2017
Line 3:		Line 3:
	=MoquetteMon - Augmented MQTT-Broker for Testing=		=MoquetteMon - Augmented MQTT-Broker for Testing=

	REM The ~~software is work in progress~~; no code or binaries have been released yet (~~June~~ 2017).		REM The first working version has been created; no code or binaries have been released yet (July 2017).

	When testing self-built IoT devices I found that sometimes it would be helpful to know what is going on from the MQTT broker's point of view. It looks like there are no MQTT brokers with monitoring capabilities, which is why I decided to roll my own add-on. Which broker to choose as a base? While Mosquitto is a popular open source MQTT broker, it is written in C. There is nothing wrong with C per se; I started out programming in 6502 Assembler "some time ago", and C and C++ are familiar. But, since the 90s I definitely prefer Java, and Moquette is open source, and written in Java. Additionally it has a well-designed, clear architecture and consists of very readable code.		==Why Moquette?==

	So Moquette it is! Moquette has a built-in feature for intercepting certain client/broker interactions. ~~Since~~ I ~~wanted~~ to ~~have access~~ to ~~more information than provided I injected~~ my ~~own code into a (very few) select locations~~.		When testing self-built IoT devices I found that sometimes it would be helpful to know what is going on from the MQTT broker's point of view. It looks like there are no MQTT brokers with monitoring capabilities, which is why I decided to roll my own add-on. Which broker to choose as a base? While Mosquitto is a popular open source MQTT broker, it is written in C. There is nothing wrong with C per se; I started out programming in 6502 Assembler "some time ago", and C and C++ are familiar. But, since the 90s I definitely prefer Java, and Moquette is open source, and written in Java. Additionally it has a well-designed, clear architecture and consists of very readable code. Kudos to the programmer, Andrea Selva.

			So Moquette it is! Moquette has a built-in feature for intercepting certain client/broker interactions. All I had to was adding Moquette as a Maven dependency to my project.

	What an MQTT client like MQTT-Spy can't show, but MoquetteMon can reveal:		What an MQTT client like MQTT-Spy can't show, but MoquetteMon can reveal:
Line 22:		Line 24:
	* Generally mismatches between subscriptions and publications (nobody is subscribed to a topic that is used for publishing)		* Generally mismatches between subscriptions and publications (nobody is subscribed to a topic that is used for publishing)
	* You want to get a global view of what your IoT circus is doing		* You want to get a global view of what your IoT circus is doing

			==MoquetteMon==

			MoquetteMon is a Java application. The main window has three tabs:

			* Clients. Identified by their MQTT ID the remote IP and the time of the last ping is shown.
			* Topics: Publications. Published topics are shown as a tree on the left. A table on the right lists details such as who has been publishing messages with this topic, the time of the last publication, the last payload, and who has subscribed to the topic.
			* Topics: Subscriptions. Subscribed to topic patterns are shown as a tree on the left. A table on the right side lists details who has been publishing messages with this topic, the time of the last publication, the last payload, and who has subscribed to the topic.

			I'm planning to add:

			* Clients: Publications. Who is publishing what?
			* Clients: Subscriptions. Who is subscribed to what?


	[[Tools]]		[[Tools]]

Ctreber at 19:33, 3 July 2017

2017-07-03T19:33:12Z

← Older revision		Revision as of 19:33, 3 July 2017
Line 9:		Line 9:
	So Moquette it is! Moquette has a built-in feature for intercepting certain client/broker interactions. Since I wanted to have access to more information than provided I injected my own code into a (very few) select locations.		So Moquette it is! Moquette has a built-in feature for intercepting certain client/broker interactions. Since I wanted to have access to more information than provided I injected my own code into a (very few) select locations.

	MoquetteMon ~~shows~~:		What an MQTT client like MQTT-Spy can't show, but MoquetteMon can reveal:

	* Which clients have connected to the broker from which IP address, and when. And when they last sent a message		* Which clients have connected to the broker from which IP address, and when. And when they last sent a (any) message, like a ping.
	* Which topics have been subscribed to, by which client		* Which topics have been subscribed to, by which client
	* For which topics messages have been published, by which client		* For which topics messages have been published, by which client

Ctreber at 11:45, 3 July 2017

2017-07-03T11:45:27Z

← Older revision		Revision as of 11:45, 3 July 2017
Line 1:		Line 1:
	[[~~IoT with AME\|Home~~]]		[[Tools]]

	=MoquetteMon - Augmented MQTT-Broker for Testing=		=MoquetteMon - Augmented MQTT-Broker for Testing=
Line 23:		Line 23:
	* You want to get a global view of what your IoT circus is doing		* You want to get a global view of what your IoT circus is doing

	[[~~IoT with AME\|Home~~]]		[[Tools]]

Ctreber at 21:11, 30 June 2017

2017-06-30T21:11:49Z

← Older revision		Revision as of 21:11, 30 June 2017
Line 1:		Line 1:
			[[IoT with AME\|Home]]

	=MoquetteMon - Augmented MQTT-Broker for Testing=		=MoquetteMon - Augmented MQTT-Broker for Testing=

Ctreber: Ctreber moved page MoqMon to MoquetteMon without leaving a redirect

2017-06-29T09:17:28Z

Ctreber moved page MoqMon to MoquetteMon without leaving a redirect

← Older revision	Revision as of 09:17, 29 June 2017
(No difference)

Ctreber: /* MoquetteMon - Augmented MQTT-Broker for Testing */

2017-06-29T09:16:54Z

MoquetteMon - Augmented MQTT-Broker for Testing

← Older revision		Revision as of 09:16, 29 June 2017
Line 20:		Line 20:
	* Generally mismatches between subscriptions and publications (nobody is subscribed to a topic that is used for publishing)		* Generally mismatches between subscriptions and publications (nobody is subscribed to a topic that is used for publishing)
	* You want to get a global view of what your IoT circus is doing		* You want to get a global view of what your IoT circus is doing

			[[IoT with AME\|Home]]

Ctreber: Created page with "=MoquetteMon - Augmented MQTT-Broker for Testing= REM The software is work in progress; no code or binaries have been released yet (June 2017). When testing self-built IoT d..."

2017-06-29T09:15:50Z

Created page with "=MoquetteMon - Augmented MQTT-Broker for Testing= REM The software is work in progress; no code or binaries have been released yet (June 2017). When testing self-built IoT d..."

New page

=MoquetteMon - Augmented MQTT-Broker for Testing=

REM The software is work in progress; no code or binaries have been released yet (June 2017).

When testing self-built IoT devices I found that sometimes it would be helpful to know what is going on from the MQTT broker's point of view. It looks like there are no MQTT brokers with monitoring capabilities, which is why I decided to roll my own add-on. Which broker to choose as a base? While Mosquitto is a popular open source MQTT broker, it is written in C. There is nothing wrong with C per se; I started out programming in 6502 Assembler "some time ago", and C and C++ are familiar. But, since the 90s I definitely prefer Java, and Moquette is open source, and written in Java. Additionally it has a well-designed, clear architecture and consists of very readable code.

So Moquette it is! Moquette has a built-in feature for intercepting certain client/broker interactions. Since I wanted to have access to more information than provided I injected my own code into a (very few) select locations.

MoquetteMon shows:

* Which clients have connected to the broker from which IP address, and when. And when they last sent a message
* Which topics have been subscribed to, by which client
* For which topics messages have been published, by which client

I found this helpful in the following cases:

* Accidentally, I had two devices using the same MQTT ID. This causes the broker do disconnect one of the two devices. The monitor showed that conflict.
* A device accidentally subscribed to the wrong topics (typo) or did not subscribe to an intended topic at all
* A device published messages to the wrong topics (type) or did not publish messages to a specific topic at all
* Generally mismatches between subscriptions and publications (nobody is subscribed to a topic that is used for publishing)
* You want to get a global view of what your IoT circus is doing