selected in the Breakdown below, with the color-coded
chart comparing performance above.
The Insights tab is designed to help you quickly iden-
tify the relevant categories that contribute the most
to the negative score in the selected metric. For ex-
ample, in Figure 6, I’m looking at Rebuffer Frequency,
By clicking Insights, I see that the larg-
est contributor to the negative score was
the set of viewers watching on the Android
OS, which experienced 4. 16 rebuffer events/
minute, and the Chrome Mobile browser
( 3.62/minute). This tells me that I may have
issues with the Android player. The next
item in the Insights panel (which I’ve blurred
out) is a specific video. It exhibited 4 rebuf-
fer events/minute, which may indicate an
Click Video Views, and you can access
the more recent video views in the defined
time frame, but only the application name
and OS were shown, not the title of the vid-
eo or any statistics. I found it more useful
to access video views from the left tab on
Figure 3, since that identifies the title as
well. Either way, you can click into the view
shown in Figure 7 on page 170 to get a feel
for the video playback experience and see
more details beneath the graph regarding the player
used, viewers, and other metrics, like total rebuffer
duration. The one thing I found missing was a way to
access the viewer experience score for that particular
view, which would have been informative (Mux plans
to add this feature in the future).
What Went Wrong on Dec. 2?
With this as a prologue, let’s dive into figuring out
what went wrong on Dec. 2 (see Figure 8 on page 170).
Using the time frame control at the upper-right corner, I can call up the data for that day and click Insights to see which experience contributed the most
to the negative score. It looks like one viewer on a Linux system was having a very bad day.
By clicking video/ogg, I can dig even deeper into the
data and see the videos that this viewer attempted to
play. By clicking a video, I can access the specific details of that attempted play (see Figure 9 on page 170),
including player, OS, CDN, ASN, and video source.
Something was obviously very wrong.
At this point, I might look in the Errors tab to see if
the system reported any errors that day. This reveals
the information shown in Figure 10 on page 170. It
looks as if the media called for by the player simply
wasn’t available. Since there was nothing to deliver,
the playback failed.
Clicking the Code 4 error opens the screen shown
in Figure 11 on page 170, which allows me to sort by
Browser, Country, OS, and other parameters. After
Firefox is delivering a noticeably poorer quality of experience than Chrome for this Mux customer.
Insights identifies the major contributors to a negative score in each category or subcategory.