At Conviva, we continuously drive towards greater data insights and actionability. Our AI Alerts enables automatic anomaly detection and key issue root cause analysis to prevent impact to your service. Last fall, we enhanced the actionability of CDN related AI alerts with the CDN ecosystem module. But alerts are only effective when they reach the right people at the right time.
We are now introducing alert severity awareness. This feature allows publishers to be notified of alerts based on severity level, and then direct the alerts to the right channels for action. You can now configure a single alert to send emails or chat notifications for relatively low-urgency issues, and to page the on-call engineer if the situation gets worse. For each alert state, we provide the list of impacted viewers which you can correlate with viewer reported issues as well as other external logs. You can configure 3 levels of severity information (info, warning and critical), based on time of impact and number of impacted viewers.
With notification tiering, alerts can be tailored so that minor issues don't awaken anyone in the middle of the night, and no major issues are missed. With the right people getting the alerts over the right channels, you can reduce alert fatigue significantly!
As part of this update we have partnered with PagerDuty to offer out of the box integration that allows you to direct critical alerts to PagerDuty tools.
We are excited to bring you this capability and drive actionability further in our alerting functionality.
Metric of the Month - Connection Induced Rebuffering Ratio
Rebuffering occurs when the video stalls during playback and the viewer must wait for the video to resume playing. Various connection, bitrate, and player issues can lead to these stalls, but so can user initiated seek events. As a result, it is important to distinguish between seek-initiated rebuffering and non-seek rebuffering. Conviva’s Connection Induced Rebuffering Ratio (CIRR) metric refines rebuffering analysis to measure only non-seek or system-induced rebuffering.
The nonseekRebufferingTime in a video stream is the total time during which the reported player-state is "buffering", and excludes the buffering time before the first frame of a video is displayed, buffering following user-initiated seeks (S1 in the diagram) and any paused time. To clearly distinguish the source of rebuffering, CIRR only counts rebuffering that starts 10 seconds or more after a seek start event as connection induced rebuffering. Otherwise, the rebuffering is counted toward seek-induced rebuffering and included in the Rebuffering Ratio metric.
Conviva measures connection induced rebuffing as the percentage of total viewing time (playingTime and rebufferingTime) during which nonseekRebufferingTime occurred in the selected period. Using all rebufferingTime in the denominator of this calculation enables a more precise measurement of system-induced rebuffering over the viewer’s total viewing time.
From the viewer perspective, the viewer impact is similar to the Rebuffering Ratio metric-- the video stalls during playback while the viewer endures the spinning wheel on screen and waits for the video to resume playing. A high Connection Induced Rebuffering Ratio or a significant increase in this metric often indicates an overall decline viewer experience and video streaming performance, often leading to an increase in the likelihood of viewer abandonment.
Summaries and Correlation
For analysis, this metric is presented as a summary and time series to display metric values as data points to baseline and highlight changes. For correlation, this metric is available in Custom and Engagement Dashboards as a distribution of play duration and Ended Plays.
In addition, the Diagnostics page can be set to show Connection Induced Rebuffering Ratio along with the Rebuffering Ratio metric to highlight the impact non-seek, system-induced rebuffering.
You can use also MetricLens dimensions to filter this metric by metadata segments for enhanced root cause analysis. For example, limiting data to a specific ISP, video asset, or player dimensions can highlight the source of changes in Connection Induced Rebuffering Ratio to a known provider, asset, or player type.
To limit the impact of prolonged rebuffering, if a session has continuous nonseek rebuffering for 30 minutes, the play is treated as expired.
Visit the Metric Dictionary in the Pulse Help Center to learn more about Conviva's metrics.
Conviva at NAB
Meet us at Conviva’s Fairway Villa - Wynn Las Vegas
Monday, April 8 – Wednesday, April 10
Learn how Conviva, the real-time measurement and intelligence platform for streaming TV, enables you to drive engagement, increase monetization, and improve the viewer experience. Make your way to our Fairway Villa at the Wynn Las Vegas to hear more about the latest innovations in streaming.
Request a meeting to talk to our team, we're looking forward to seeing you.
This month we updated the following sensors: