MQTT (Message Queueing Telemetry Transport) protocol is a publish/subscribe-based, lightweight messaging protocol for machine-to-machine (M2M) communication over TCP/IP. The first version of the MQTT protocol was authored by Stanford-Clark, IBM, and Arlen Nipper. Catchpoint's points MQTT Test monitors the performance and availability of IoT (Internet of Things) devices by publishing and/or subscribing to messages for a specified topic and measuring how long it takes to communicate.
MQTT Test Properties | |
|---|---|
| Name | A name used to identify this test. |
| Description | Optional additional information about the test |
| Test Location | The path to the IoT device being monitored. (e.g. mqtt://test.mosquitto.org:1883) |
| Subscribe Topic | The topic of messages the test will attempt to receive from the device. A topic consists of one or more topic levels. Each topic level is separated by a forward slash. Please note that topic is case-sensitive. |
| Publish Topic | The topic of messages the test will attempt to send to the device. |
| Publish Message | The content to be published to the device. |
| Certificate | A PKCS#12 Certificate which the device will recognize to authenticate test communications. Click Add Certificate to select a certificate from the Library or to add a new certificate. |
| Authentication | By default, the test will run Anonymously (no authentication.) By clicking "Add User Name and Password" you can select credentials from the credentials library, or add new credentials. |
| Location | The Product/Folder location of this test (read only) |
| Status | Determines whether this test is current Active or Inactive |
Supported Metrics | |
|---|---|
| # Runs | Total number of test runs for the defined time period. |
| # Test Errors | The total number of test runs that failed. This is the sum of all of the following types of test failures:
|
| % Availability | The percentage of test runs where server was reached and the test was completed (i.e. there was not a Test Error.) Availability is calculated as: (# Test Runs - # Test Errors) / # Test Runs |
| % Frustrated | The percentage of test runs that exceeded the Apdex “frustrated” threshold. |
| % Not Frustrated | The percentage of test runs that completed in less time than the Apdex “frustrated” threshold. This is equivalent to: % Satisfied + % Tolerating |
| % Satisfied | The percentage of test runs that completed in less time than the Apdex “Satisfied” threshold. |
| % Tolerating | The percentage of test runs that exceeded the Apdex “Satisfied” threshold but completed in less time than the “Frustrated” threshold. |
| Apdex | A scoring mechanism that translates performance metrics of diverse applications into generic “User Satisfaction” levels using predefined response time thresholds. You can use default Apdex thresholds or configure your own on a per basis. For more details about Apdex, visit http://www.apdex.org/ |
| Connect (ms) | The time it took to establish a TCP connection with the server. |
| DNS (ms) | The time it took to resolve the domain name to an IP address. |
| Experience Score | A composite metric that captures the overall experience of a user on a scale of 0-100. |
| Publish Size (bytes) | The size of the MQTT Message published. |
| Publish Time (ms) | The time it took to publish the MQTT Message. |
| Signal Quality | Measures the quality of the WLAN connection in terms of data transfer speed. It indicates what percent of the available network are you using to move data (upload / download). 99% is as good as it gets in terms of signal quality. |
| Signal Strength (dBm) | This number represents the power the clients device is receiving from the Access Point / Wi-Fi router. A number of -30 dBm indicates excellent while a number of -70dBm indicates very poor signal strength. |
| Subscribe Size (bytes) | The size of the retrieved MQTT message in bytes. |
| Subscribe Time (ms) | The time it took to retrieve the MQTT message. |
| Test Time (ms) | One cohesive metric that applies to all test types and indicates the total duration of the test run. Test Time is equivalent to Response, Test Response (Transaction and web tests) and ping RTT (Trace Route tests), and is used when calculating Apdex. Test Time is not available for Request, Host, or Zone charting. |