As a developer I need to verify whether time measurement changes introduced in #1471 and delivered in version 18.0.0 result in better QoS/QoE measurements.
Remark
#1471 improved how time is measured but we might still observe large QoS/QoE timings since suspending clocks continue to tick when a device is charging. We should observe a smaller amount of large values, though.
Hints
The following Lucene query might be helpful:
session.player.platform:Apple AND session.qoe_timings.total:>500000 AND session.player.version:18.0.0
Acceptance criteria
- Version 18.0.0 has been compared with earlier versions on our monitoring platform.
- If large timings can still be observed this known issue is mentioned in our documentation.
- A monitoring improvement has been proposed if meaningful (e.g. switching to the mean instead of the average).
Tasks
As a developer I need to verify whether time measurement changes introduced in #1471 and delivered in version 18.0.0 result in better QoS/QoE measurements.
Remark
#1471 improved how time is measured but we might still observe large QoS/QoE timings since suspending clocks continue to tick when a device is charging. We should observe a smaller amount of large values, though.
Hints
The following Lucene query might be helpful:
session.player.platform:Apple AND session.qoe_timings.total:>500000 AND session.player.version:18.0.0Acceptance criteria
Tasks