# Media Live Logs

The IOIO Live Workflows service allows to see the Media Live channel logs for a particular workflow that's running or has been running.

How it works:

• There is a dedicated endpoint for Media Live logs in the Live Service Swagger.

• The endpoint accepts the following query parameters:
  • workflowId: string field which accepts the id of a workflow for which we want to see the logs.
  • pipeline: the pipeline field accepts an integer value of 0 or 1. For workflows which are of type STANDARD there are two pipelines and the logs for each of the two pipeline can be viewed when set to 1 or 0.
  • startDateTime: a string field which accepts a string with date-time in the following format: 2022-01-05T15:00:00.000Z. If no value is set the the default value is the channel start time.
  • endDateTime: a string field which accepts a string with date-time in the following format: 2022-01-05T15:00:00.000Z. If no value is set the the default value is the channel stop time.
  • pageSize: accepts an integer with its whole purpose of being to limit the results per page. Default page size is 300 results.
  • forwardToken: When the results are more than one page the forwardToken can be used to view the next page by being sent as a query parameter.
  • backwardToken: When going through the results pages to return to the previous page there will be a backwardToken in the results. It's being used in the same way as the forwardToken but in this case we are going back through the pages.

{
  "items": [
    {
      "severity": "I",
      "timestamp": "2022-01-06T09:18:22.681194",
      "message": "Processing stop command..."
    },
    {
      "severity": "I",
      "timestamp": "2022-01-06T09:18:22.681454",
      "message": "RTMP reader for [rtmp://localhost:1935/ioio/primary] read 0 buffers for a total of 0 bytes, closing."
    },
    {
      "severity": "I",
      "timestamp": "2022-01-06T09:18:22.681755",
      "message": "Clearing alert: [5201] [ProbeVideoLoss] [5201-ProbeVideoLoss] [[1] Video not detected: Check input signal]"
    },
    {
      "severity": "I",
      "timestamp": "2022-01-06T09:18:22.681792",
      "message": "Clearing alert: [5101] [ProbeAudioLoss] [5101-ProbeAudioLoss] [[1] Audio not detected: Check input signal]"
    },
    {
      "severity": "W",
      "timestamp": "2022-01-06T09:18:22.681815",
      "message": "Failed to probe input: Halted"
    },
    {
      "severity": "I",
      "timestamp": "2022-01-06T09:18:22.861929",
      "message": "Clearing alert: [5305] [1_1_0:primary] [5305-1_1_0:primary] [Searching for RTMP Push stream [primary], which does not exist at this time]"
    },
    {
      "severity": "I",
      "timestamp": "2022-01-06T09:18:23.681916",
      "message": "Clearing alert: [5007] [Initial Probe] [5007-Initial Probe] [Halted]"
    }
  ],
  "forwardToken": "f/36605796891003951230917692842812845874819555045573328896/s",
  "backwardToken": "b/36605796868703206032387069700018853490297109004870877184/s"
}

Note the severity strings in the above example. The letters which are displayed in the severity are:

• D - Debug: includes debug messages, info, warning, critical and fatal messages.
• I - Information: presents information for the Media Live Channel and its unputs.
• W - Warning: presents warnings like in our example that the input has been failed to probe.
• E - Error: includes critical and fatal messages.

NOTE: You should not automate any processing based on the wording in these logs because that wording is subject to change without notice.