Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


This page describes how Cloud Injector Tag Agent configurations interact with Ignition tag trees to push messages and tags to a Cloud service or IoTHub. It  It explains how tags get identified and goes over some example configurations to show how the system will behave in different scenarios.


Like the MQTT Transmission Transmitter, the Cloud Injector Tag Agent is designed to pick up tags in Ignition or Ignition Edge and publish push those tags, parts of their configuration, and tag change events to a Cloud service.  Which tags are published pushed to the Cloud is based on a combination of an Agents configuration as well as the arrangement of tags in the Ignition tag tree.

(Are these paragraphs below relevant to the Tag Agent ?   Are they using the proper verbs and nouns ?)

It is important to note that the configuration of the tag agent in conjunction with the tag tree determines what MQTT topics data is published on. The MQTT topics are essentially the 'addresses' of the different components in the distributed system. In the topics, per the Sparkplug specification, there are three important identifiers to note. These are shown below.(Is this paragraph below relevant to the Tag Agent ?)

These identifiers then become components of the MQTT topics. There is also a 'verb' in Sparkplug messages which denotes whether the message is a birth certificate, death certificate, data message, command message, etc. Sparkplug topics are of the following form using all of these different parameters.