Monitoring Rules and Metrics

Define the thresholds that mark a Live Slicer unhealthy, and the metrics those rules are evaluated against.

Monitoring Rules

Use rulesets to define rules that identify the metrics to monitor and the thresholds for warning/critical levels.

Key Information

  • By default, Live Slicers are monitored using a default set of read-only monitoring rules. However, you may assign a custom set of monitoring rules to one or more Live Slicers.
  • View your custom monitoring configurations from the Monitoring Rules page.
  • Once you have created a custom monitoring configuration, you may reassign a Live Slicer to it. The previous set of monitoring rules (e.g., Default) will no longer apply to the Live Slicer, since a Live Slicer may only be associated with a single set of monitoring rules at any given time.
  • All metrics, with the exception of Closed Captioning Last Seen, are updated every 4 seconds. The Closed Captioning Last Seen metric is updated every 10 seconds.
  • The Live Slicer only reports monitoring data when slicing content. It cannot report data when it is in another state (i.e., ad break, replace content, or blackout), since it is not receiving a video feed.
  • A user with either the admin or read/write permission can create rulesets that can be leveraged by any member of your organization. This type of ruleset is known as an organization ruleset.

Create a Custom Set of Monitoring Rules

  1. Navigate to the Monitoring Rules page.

    • From the main menu, navigate to Services.
    • Select Monitoring 2.0.
    • Navigate to Settings > Monitoring Rules.
  2. Organization: Admin and Read/Write Users: Determine whether a ruleset will be created for your organization or for personal use. From the Organizations option, select either your organization or Personal.

  3. Select + Create New Ruleset.

    • Enter the name for the ruleset in the Ruleset Name field.
    • Configure each metric that should trigger warning/critical status.
      • Find the desired metric.
      • Select either Warning or Critical from the Severity option.
      • Define the conditions under which the metric will change health states.
        • States: Configure the Set option to the number of seconds that the sub-optimal state (e.g., no signal, no closed captions detected, or black video was detected) must persist before the Live Slicer's health will change to the severity defined in the Severity option. Configure the Clear option to the number of seconds that the optimal state must persist before the Live Slicer's health will change back to healthy.
        • Measurements: Configure the Set Threshold option to the condition that must be met for the number of seconds defined in the Set Duration option before the Live Slicer's health will change to the severity defined in the Severity option. Configure the Clear Threshold option to the condition that must be met for the number of seconds defined in the Clear Duration option before the Live Slicer's health will change back to healthy.
  4. Repeat the above steps as needed.

  5. Select Save.

Modify a Custom Set of Monitoring Rules

  1. Navigate to the Monitoring Rules page.

    • From the main menu, navigate to Services.
    • Select Monitoring 2.0.
    • Navigate to Settings > Monitoring Rules.
  2. Organization: Admin and Read/Write Users. Determine whether to modify a ruleset that was created for your organization or for personal use. From the Organizations option, select either your organization or Personal.

  3. Select the desired ruleset.

  4. Review and modify the conditions under which metrics will change health states as needed.

  5. Select Save.

Delete a Custom Set of Monitoring Rules

  1. Navigate to the Monitoring Rules page.

    • From the main menu, navigate to Services.
    • Select Monitoring 2.0.
    • Navigate to Settings > Monitoring Rules.
  2. Organization: Admin and Read/Write Users. Determine whether to delete a ruleset that was created for your organization or for personal use. From the Organizations option, select either your organization or Personal.

  3. Mark each desired ruleset.

  4. Select Delete Selected Rulesets.

  5. Select Yes, Delete It.

Assign a Custom Set of Monitoring Rules to One or More Live Slicers

  1. Navigate to the Monitoring Rules page.

    • From the main menu, navigate to Services.
    • Select Monitoring 2.0.
    • Navigate to Settings > Monitoring Rules.
  2. Determine whether you will map a ruleset that was created for your organization or for personal use. From the Organizations option, select either your organization or Personal.

  3. Select Ruleset Mappings.

  4. From the 1. Choose a Ruleset to Apply option, select the desired custom monitoring configuration.

  5. Optional. Use the Search field to filter the list of available Live Slicers by name and owner.

  6. Mark the desired Live Slicers.

  7. Select Apply Ruleset to Selected Slicers.

    💡

    Alternatively, you may assign a ruleset to a Live Slicer from the Live Slicer Monitoring dashboard by selecting the desired Live Slicer and then selecting the rule set that will be applied to it from the Ruleset option.

Assign the Default Set of Monitoring Rules to One or More Live Slicers

  1. Navigate to the Monitoring Rules page.

    • From the main menu, navigate to Services.
    • Select Monitoring 2.0.
    • Navigate to Settings > Monitoring Rules.
  2. Determine whether you will map a ruleset that was created for your organization or for personal use. From the Organizations option, select either your organization or Personal.

  3. Select Ruleset Mappings.

  4. Optional. Use the Search field to filter the list of available Live Slicers by name and owner.

  5. Mark the desired Live Slicers.

  6. Select Remove Ruleset from Selected Slicers.


Metrics

A description for each monitoring metric is provided below.

MetricDetails
Ad Last SeenDetermines the length of time that may elapse since the end of the last ad break before triggering a warning/critical status.
The Live Slicer resets this metric upon changing state (e.g., Slicing, Replacing Content, and Blackout)
Troubleshooting
Check whether ad breaks are being triggered.
Black VideoDetermines the length of time that black frames may be sent by a Live Slicer before triggering a warning/critical status.

This rule measures the duration of black video by averaging the video's luminosity percentage over the last few seconds.
📘

Periods of black video may be normal. Consider the source content when setting critical/warning thresholds.


Diagnosis
Check the luma response parameter for a very low value.

Troubleshooting
Check the source feed to resolve issues with video input.
Closed Captions Last SeenIndicates the amount of time since the Live Slicer received closed captioning data.

Key Information:
  • This metric is reported in 10 second intervals.
  • This rule is inapplicable when closed captioning data has not been received from the Live Slicer.
  • Consider the content when setting the threshold for this metric. Some content may contain an extended time period without closed captioning data.

Troubleshooting
Check the source feed.
Dropped FramesDetermines how many frames may be dropped within the current reporting period before triggering a warning/critical status.
📘

This metric requires Live Slicer version 16031400 or higher.

Extended Ad BreakDetermines the maximum duration of an ad break before triggering a warning/critical status.

Troubleshooting
Verify that automation scripts are sending valid ad break instructions to the Live Slicer. Also, verify that the Live Slicer is acting upon those instructions.
Last Update TimeIndicates the amount of time since an update from the Live Slicer was received. A high value for this metric is indicative of one of the following conditions:
  • The Live Slicer was shut down.
  • Internet connectivity issues. If there are other Live Slicers in the same datacenter or location, then this issue may be confirmed by whether they are also reporting a high value for this metric.

Troubleshooting
Check for an egress bandwidth issue.
Loss of AudioDetermines the length of time during which audio is not detected before triggering a warning/critical status.

Periods of silence may be normal. Consider the source content when setting critical/warning thresholds.

Diagnosis
Check the vol response parameter for a very low value.

Troubleshooting
Check the source feed to resolve issues with audio levels.
Nielsen Tag Last SeenDetermines the length of time that may elapse since the Live Slicer last received a Nielsen watermark before triggering a warning/critical status.

Key Information:
  • Nielsen watermarks may be inserted into the audio stream sent to the Live Slicer. They are typically inserted at 10 second intervals. However, this interval may vary according to your implementation.
  • Nielsen watermarks are leveraged by the Live Slicer to generate ID3 tags through which a media player reports viewership data.

Troubleshooting
Check whether Nielsen watermarks are being inserted into the audio stream fed to the Live Slicer.
Processing BacklogDetermines how many packets may be queued to be read by the Live Slicer before triggering a warning/critical status.

Key Information:
  • The recommended levels for this metric vary according to the signal type. For example, a UDP Unicast stream should have a much lower threshold (e.g., 1,000) than a UDP Multicast stream (e.g., 10,000).
  • A high value may indicate insufficient CPU resources on the computer hosting the Live Slicer.
  • A transient spike in this metric may not be cause for concern.

Troubleshooting
Check for insufficient resources.
SCTE Last SeenDetermines the length of time that may elapse since the Live Slicer last received a SCTE 35/104 signal before triggering a warning/critical status.
Signal StatusDetermines whether a loss of the Live Slicer's signal will trigger warning or critical status.

A loss of signal is also indicated in the Live Slicer's thumbnail preview by green/black frames or a predefined background image.
Static AudioDetermines the length of time during which static audio is detected before triggering a warning/critical status.

Static audio is detected by analyzing the audio's loudness percentage over the last few seconds. This rule ignores periods of silence.

Diagnosis
Check the vol response parameter for a static value.

Troubleshooting
Check the source feed to resolve issues with audio levels.
Static VideoDetermines the length of time during which static video (e.g., green screen, color bars, or a frozen frame) is detected before triggering a warning/critical status.

Static video is detected by analyzing the video's average luminosity percentage over the last few seconds.

Diagnosis
Check the luma response parameter for a static value.

Troubleshooting
Check the source feed to resolve issues with video input.
Upload QueueDetermines how many slices may be queued for upload before triggering a warning/critical status.

Diagnosis
A value higher than 2 may indicate Live Slicer connectivity issues.

Troubleshooting
Check for an egress bandwidth issue.


Did this page help you?