Troubleshooting Sparkplug Host Applications

Sparkplug is a trademark of Eclipse Foundation, Inc. "MQTT" is a trademark of the OASIS Open standards consortium. Other related terms are trademarks of their respective owners. Any use of these terms on this site is for descriptive purposes only and does not imply any sponsorship, endorsement or affiliation.

Introduction

This article discusses issues specific to troubleshooting Sparkplug host applications. For information that is common to any troubleshooting in Sparkplug, see Sparkplug Troubleshooting.

Common issues

Incorrect identification information

You can suspect an identification mismatch if your host application receives information from a wrong source, or does not receive any information whatsoever. If this cannot be resolved by correlating the identification information of the source (such as what you *think* is the Sparkplug group ID or edge node ID) with the information used in the Sparkplug host application, you can use the SparkplugCmd Utility for figuring out the true information used by the producer.

To do so, use the SparkplugCmd utility in the role of a "universal" Sparkplug host application. And, let it subscribe to everything in the MQTT broker. Then, analyze the output, and find out what the actually used identification information is (e.g. group IDs, edge node IDs, and/or metric names). With that, you can then decide whether it is the producing side (Sparkplug edge node) that needs to be fixed (reconfigured), or the consuming side (Sparkplug host application).

Example

• The following commands in SparkplugCmd subscribe to all payload notifications from Sparkplug edge nodes and devices on "mqtt://test.mosquitto.org":

consumer mqtt://test.mosquitto.org
subscribePayload