Skip to main content

Recording Templates

A recording template defines how a live stream is captured to persistent storage. When a stream matching the template's domain, application, and stream name pattern is ingested, the platform automatically records the stream according to the specified format and path configuration.

![Figure Needed] Screenshot of recording templates listing interface

Template List Columns​

ColumnDescription
NameUnique identifier for the recording template
DomainThe ingest domain this template applies to
AppThe application name scope (supports wildcards)
StreamThe stream name scope (supports wildcards)
Screenshot FormatThe container or file format used for recorded output (e.g., MP4, FLV, HLS)
PathThe storage path or bucket prefix where recordings are saved
StatusWhether the template is enabled or disabled
CreatedTimestamp when the template was created
OperationsAvailable actions: Modify or Delete

Creating a Recording Template​

  1. Navigate to Media Processing > Recording Templates.
  2. Click Add Template.
  3. Enter a unique template name.
  4. Select the target Ingest Domain.
  5. Specify the App and Stream name patterns.
  6. Select the Recording Format.
  7. Define the output Path.
  8. Set the template Status to enabled or disabled.
  9. Click Save.
tip

Use timestamp variables in the Path field to organize recordings chronologically. This prevents output files from being overwritten when a stream restarts.

Modifying a Recording Template​

  1. Locate the template in the list.
  2. Click Modify in the Operations column.
  3. Update the required fields.
  4. Click Save.
caution

Modifying a recording template affects only streams that begin ingesting after the change is saved. Streams already in progress continue to use the configuration that was active at the time recording started.

Deleting a Recording Template​

  1. Locate the template in the list.
  2. Click Delete in the Operations column.
  3. Confirm the deletion when prompted.

Deleting a template stops future recordings that would have matched its scope. Recordings already written to storage are not affected.