Skip to main content
Version: 3.4.x

TGDM Recording

TGDM also works from Moth URIs, similarly to Mantis.

  1. A recording start condition occurs because of device connection, Workflow Run start, or a manual operator request.
  2. The Server calculates the Moth URI of the target Track.
  3. The Server sends a recording-start request to TGDM.
  4. TGDM returns a recording id.
  5. The Server stores the Recording state as STARTED.
  6. On device disconnect, Workflow end, or manual stop, the Server sends a recording-stop request to TGDM.
  7. The Server stores the Recording state as STOPPED.

Recording start policies​

  • Automatic recording: starts when the device connects and stops when it disconnects
  • Workflow recording: starts when the Workflow Run starts and stops when it completes or fails
  • Manual recording: starts or stops through operator API calls per device

In short, TGDM is a real-time stream consumer, while CoBiz Server is the recording lifecycle orchestrator.