Page History

...

Rebirth Requests (available 4.0.22 onward)

Rebirth Count

Integer

The count of rebirth requests issued by MQTT Engine

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

...

)

Rebirth (Last DateTime)

DateTime

The time of the last rebirth request issued by MQTT Engine

Rebirth (Last) Cause

String

The reason for the last rebirth request

Reasons for rebirth requests are:

Triggered by user
- A rebirth request for the Edge Node was manually triggered at MQTT Engine
Message sequence number error
- In a Sparkplug compliant system, the combination of Group ID and Edge Node ID (the Sparkplug Edge Node Descriptor) that identifies the Edge Node must be unique.
- If there are two or more Transmitters with the same Sparkplug Edge Node Descriptor, data from these two transmitters will sent with the same topic resulting in the next message sequence number expected by the MQTT client being incorrect. As a result, the MQTT Client will mark the data as stale and request a rebirth from the transmitter.
- If you have multiple MQTT Clients subscribing to the namespace, this will also likely create a firestorm of rebirth requests across the system.
Received a message for an edge node that is offline
- A DDATA or NDATA message was received from an Edge Node that is marked as Offline at MQTT Engine.

...

The reason for the last rebirth request

...

...

Versions Compared