Versions Compared

Old Version 7

changes.mady.by.user Gill Houghton

Saved on

compared with

New Version Current

changes.mady.by.user Gill Houghton

Saved on

Key

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

MQTT Transmission automatically creates a known set of folders (in the MQTT Transmission provider) containing tags for Transmission Control and Transmission Info.

...

For each Transmitter, a tag tree will be created with the tag path of TransmitterName > Tag Path > GroupID > EdgeNodeID

NameData TypeDescription
Enable Tag TrackingBooleanWritable tag to control whether or not to update Tags Per Seconds (added 4.0.17)
Largest Mesg Xmit (bytes)LongThe largest message size in bytes sent by the Edge Node since the last time the metrics were reset via the Edge Node Reset Metrics tag
Largest Mesg Xmit TimestampDateTimeThe time at which the largest message was sent by the Edge Node since the last time the metrics were reset via the Edge Node Reset Metrics tag
Last RefreshDateTimeThe time at which the last Edge Node refresh request was completed
Refresh Edge NodeBooleanA writeable tag to request a refresh of the Edge Node. This will force the Edge Node to disconnect and reconnect resulting in the sending of NDEATH, NBIRTH and DBIRTH messages
Refresh RequiredBooleanA tag indicating the new tags have been identified by Transmission for this Edge Node and a refresh is required.
Reset MetricsBooleanA writable tag to reset the metrics for this Edge Node
Tag CountLongThe number of tags identified for this Edge Node
Tags Per SecondLongThe number of tags changes published per second with the value updated every two seconds (added 4.0.17)
Total Bytes Xmit (bytes)LongThe number of bytes sent by the Edge Node since the last time the metrics were reset via the Edge Node Reset Metrics tag
Total Mesg XmitLongThe number of messages sent by the Edge Node since the last time the metrics were reset via the Edge Node Reset Metrics tag

...

For each History Store, a folder will be created with the name of the History Store

NameData TypeDescription
Disk UsedLong

Created if the History Store type is Disk_Backed and shows the memory used since last module restart. This parameter will never go to zero for the following reasons:

  • The initial config of the DB will contain empty seeded tables based on the number of edge nodes and devices (table per edge node and per device) and at least one metadata table.

  • Flushed rows are marked for deletion and will actually be deleted from the DB on its internal schedule. This is to minimize the writes on a flash/SSD drive.

Memory UsedLongCreated if the History Store type is In_Memory and shows the memory used since last module restart


Under each of the History Store folders, for each Transmitter, a tag tree will be created with the tag path of GroupID > EdgeID  and/or > DeviceID

NameData TypeDescription
Metrics
Percentage Used
Stored
Float
Long

Number of Edge Node or Device level tag change events stored

as a percentage of the configured

  • For Disk_Backed History Store, this tag is updated every 30 seconds
Records StoredLong

Number of Edge Node or Device

Tag CapacityMetrics StoredLong

level records stored

  • For Disk_Backed History Store, this tag is updated every 30 seconds
Metrics Percentage UsedFloat(Deprecated 4.0.19) Number of Edge Node or Device level tag change events stored as a percentage of the configured Edge Node or Device Tag Capacity
Records Percentage UsedFloat
Records StoredLong
(Deprecated 4.0.19) Number of Edge Node or Device level
records stored
tag change events stored as a percentage of the configured Edge Node or Device Record Capacity