Versions Compared

Old Version 2

changes.mady.by.user Gill Houghton

Saved on

compared with

New Version 3

changes.mady.by.user Gill Houghton

Saved on

Key

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

...

For each connected Edge Node, a Node Control and Node Info folder containing tags is created along with a Device Info folder for each connected device. The tags created in these folders are documented here

Image Added


Using these tags we can look into the health of each Edge Node connection: Image Removed


Data Latency (ms)Long

The time in milliseconds between MQTT Engine receiving of the last message and the payload's reported time.

A long latency time can indicate network issues.

Note: For this to be very accurate the edge node's clock and the system clock running MQTT Engine should be synced

...

Rebirth (Last) CauseString

The reason for the last NBIRTH message received by MQTT Engine (available 4.0.22 onward)

Options are:

  • Triggered by User
  • Message sequence number error
  • Received a message for edge node that is offline


Rebirth (Last DateTime)DateTimeThe time
at which
the last NBIRTH message received by MQTT Engine (available 4.0.22 onward)


Rebirth CountInteger

The count of NBIRTH messages received by MQTT Engine (available 4.0.22 onward)

...

A high rebirth count in a small time window is a clear indicator of issues at the Edge.




  • [MQTT Engine]Engine Info/MQTT Clients/Chariot/Chariot Server/Server Latency

...