Endpoint monitoring for a messaging framework

A method of alerting for an endpoint monitoring for a machine to machine (M2M) messaging framework by a monitoring application stored in a non-transitory memory of a monitoring server and executable by a processor of the monitoring server, said method comprising:

• periodically querying a plurality of message queue telemetry transport (MQTT) messaging brokers communicatively coupled with a plurality of MQTT clients for data regarding a count of disconnections between the plurality of MQTT messaging brokers and the plurality of MQTT clients executing in a plurality of different types of wireless endpoint devices;
• comparing the count of disconnections determined from the data received from the plurality of MQTT messaging brokers to data stored in an information data store, wherein the data in the information data store comprises a historical count of disconnections between the plurality of MQTT messaging brokers and the plurality of MQTT clients;
• determining whether the determined count of disconnections between at least one of the plurality of MQTT messaging brokers and at least one of the plurality of MQTT clients exceeds a predefined threshold of disconnections, wherein the predefined threshold of disconnections is determined based on the historical count of disconnections and a plurality of factors including an MQTT message broker and at least two of a particular time of day, a particular day of week, an application, or a particular geographic area associated with the determined count of disconnections, wherein the historical count of disconnections of the predefined threshold is determined for a periodically cyclical previously occurring combination of the at least two of the particular time of day, the particular day of week, the application, or the particular geographic area corresponding to a current combination of the at least two of the particular time of day, the particular day of week, the application, or the particular geographic area associated with the determined count of disconnections, and wherein the predefined threshold of disconnections is different for different MQTT messaging brokers;
• and
• sending an alert to a workstation and initiating corrective actions in response to a determination that the determined count of disconnections exceeds the predefined threshold of disconnections, wherein the corrective actions comprise rebooting the at least one of the plurality of MQTT clients with the determined count of disconnections that exceeds the predefined threshold and establishing a connection between a different MQTT messaging broker and the at least one of the plurality of MQTT clients with the determined count of disconnections that exceeds the predefined threshold.

A method of addressing disconnection issues for an endpoint monitoring for a machine to machine (M2M) messaging system by a monitoring application stored in a non-transitory memory of a monitoring server and executable by a processor of the monitoring server, said method comprising:

• periodically sending a plurality of message queue telemetry transport (MQTT) messaging brokers communicatively coupled with a plurality of MQTT clients a request for data regarding a count of disconnections between the plurality of MQTT messaging brokers and the plurality of MQTT clients executing in a plurality of different types of endpoint devices;
• comparing the count determined from the data received from the plurality of MQTT messaging brokers to data stored in an information data store, wherein the data in the information data store comprises a historical count of disconnections between the plurality of MQTT messaging brokers and the plurality of MQTT clients;
• determining, based on the comparison, whether the determined count of disconnections between at least one of the plurality of MQTT messaging brokers and at least one of the plurality of MQTT clients exceeds a predefined threshold of disconnections, wherein the predefined threshold of disconnections is determined based on the historical count of disconnections and a plurality of factors including an MQTT messaging broker and at least two of a particular time of day, a particular day of week, an application, or a particular geographic area associated with the determined count of disconnections, wherein the historical count of disconnections of the predefined threshold is determined for a periodically cyclical previously occurring combination of the at least two of the particular time of day, the particular day of week, the application, or the particular geographic area corresponding to a current combination of the at least two of the particular time of day, the particular day of week, the application, or the particular geographic area associated with the determined count of disconnections, and wherein the predefined threshold of disconnections is different for different MQTT messaging brokers;
• and
• initiating corrective actions in response to a determination that the determined count of disconnections exceeds the predefined threshold of disconnections, wherein the corrective actions comprise rebooting the at least one of the plurality of MQTT clients with the determined count of disconnections that exceeds the predefined threshold and establishing a connection between a different MQTT messaging broker and the at least one of the plurality of MQTT clients with the determined count of disconnections that exceeds the predefined threshold.