capabilities.work

Dolby OptiView Audit Channel Run History

A 3-step recipe with Dolby.io. We can help you get access.

Recipe · 3 steps

Dolby OptiView Audit Channel Run History

with Dolby.io · OTT & Streaming Delivery

Read a channel, its engine runs, and its transcoding-minutes analytics.

  1. Confirm the channel exists and capture its current status.
  2. List the channel's engine runs. Each run includes its engineId, start and config under data.
  3. Retrieve transcoding-minutes analytics for the channel over the requested window and resolution.
What you'll need to have ready
  • authorization: HTTP Basic Authorization header value.
  • channelId: The id of the channel to audit.
  • start: Start of the analytics period (timestamp).
  • end: End of the analytics period (timestamp).
  • resolution: Analytics time resolution (15min, hour, day, or month).
For your developer

Arazzo workflow dolby-io:audit-channel-run-history, 3 operations: get-channel → get-channel-runs → get-channel-transcoding-minutes. Specs on APIs.io.

More recipes with Dolby.io

Dolby OptiView Attach Ingest and Engine then Go LiveDolby OptiView Enable Recording Webhook and TokenDolby OptiView Inspect an Engine's Last RunDolby OptiView Provision and Start a ChannelDolby OptiView Provision a Broadcast Token with ClusterDolby OptiView Provision a Viewer TokenDolby OptiView Publish a Secured DistributionDolby OptiView Start a Single Engine and ConfirmDolby OptiView Stop a Channel and Confirm IdleDolby OptiView Tear Down a Channel