Create Introduction page with all relevant definitions of the protocol
Will add improved topics and payloads explanation;
Here allready a little sum up of what metrics can do for us;
each EoN node can share data on a broker via a set of pre-defined topic rules. The topics follow these pre defined rules while they are dynamic, when your infrastucture changes, the topics will change along. If your infrastructure grows, the topics grow accordingly, if your infrastructure shrinks, your topics shrink accordingly.
Each message consists of a single Topic in the form of a hierarchy and a payload which consists of one or several metrics and its accompanying metadata.
The Node decides what payload information will sent the broker (and thus shared to all other clients in the network which are subscribed) and wether this information is refreshed in a timely fashion or on change of the data.
So, it is up to the EoN node device how much information and what kind of meta data of the information is shared!
To provide for such flexibility, Metrics are highly flexible by nature and contain a way to expose good quality metadata and is therefore useful for many different use-cases and scenario's.
For instance providing information about the pumps, are they on or off, do they have alarms. What kind of alarm, the pumpflow, the pumpcurrent, pumptorque,the VFD speed, vfd frequency etc etc etc.Evey device can have its own topic and have its own information and metadata. Since data can be shared in a timely manner or on data change we can send a report every hour or on the moment the pump sitches on or off.
The introduction page has been revised to mention Namespaces, Payload's and Metrics.
Log in to post a comment.