The CIR Related Exits metric shows the number and percent of ended plays related to CIR. This metric considers a play end related to CIR if CIR occurred within 5 seconds of the session end.
For each session, this metric counts if the session end is related to CIR.
The aggregation of this metric shows the sum of CIR Related Exits divided by the sum of ended plays during the interval.
CIR Related Exits is an ended metric and is available only for ended sessions.
Distributions
Ended Plays vs. CIR Related Exits Distribution: a distribution by preset buckets of CIR time in milliseconds, where each bucket is the number of CIR related exits that occurred with that range of CIR time.
This distribution can help you understand your audience's tolerance for CIR performance issues and illustrates any CIR outliers' actual impact on the number of related ended plays
Note: The first bucket of zero CIR is always empty, as CIR is required for session qualification. Subsequent buckets of low CIR time (for example, 1-3 ms) may have ended due to non-CIR events (for example, a viewer exited during the start of CIR but due to another viewing issue). Use the higher CIR buckets to analyze sessions with impacts more closely aligned with higher CIR.
You can use metric filtering to diagnose only the sessions that had high percentage of dropped frames. For more details on metric filters, see Metric filtering.
The following image illustrates the CIR impact period and the calculation of session CIR time. The amount of CIR time during a session is defined as the CIR time that occurred during the CIR impact period. The impact period counts backward from the session end until a cumulative total of 30 seconds of non-CIR time occurred, or the play started.
Related Support
|
Metric Details |
Description |
|---|---|
| Dashboards and Metric Presentation |
|
| Dimensions | Use MetricLens dimensions to filter this metric by metadata segments for enhanced root cause analysis. For example, limiting data to specific ISP and player dimensions can narrow the root cause of lower bitrates to a known provider and player type. |
| Diagnostics |
The Diagnostics page presents detailed information about the CIR Related Exits in the Analysis window. For more information about diagnosis with this metric, see Diagnostics. |
| Manual Alert Support |
No. |
| AI Alert Support | No. |
| Metric Adjustment |
Application backgrounding may be considered as a session end. If the session is less than 30 seconds, the metric includes all instances of rebuffering that occurred during the session. Not available for CDN dimensions. |
For more metric definitions, see the Metric Dictionary.