STREAMING GLOSSARY
Definitions, examples and related terms for this part of your viewing setup.
TERMS & EXAMPLES
A support ticket is a recorded request that gives a service or publisher a way to track an issue and its responses. Its usefulness comes from relevant details and a clear reference, not from its length. Device, app, symptom, time and safe reproduction information can help route the issue without exposing unnecessary account secrets in the record.
Read more →Reproduction steps describe the sequence of actions and conditions that lead to a problem. They help another person distinguish a repeatable failure from an isolated observation. Good steps identify the relevant device, application and starting state, then explain what was done, what happened and what result was expected instead during that specific test.
Read more →An error log records events or diagnostic messages produced by software or infrastructure. It can help locate the stage at which an operation failed, but messages need context and interpretation. Logs can also contain private addresses, tokens or account details, so useful evidence should be reviewed and redacted before it is shared beyond the appropriate support process.
Read more →A timestamp records a point in time, often including a date and a clock value. It becomes much more useful when the time zone or offset is known. Support logs, payments and viewing incidents may use different clocks, so a precise report should connect the observed local time with the relevant date and zone for comparison.
Read more →
A service outage is a period in which a service or a defined part of it is unavailable. Its scope can be limited to particular functions, regions or infrastructure rather than every user. A household playback failure can be a symptom worth reporting, but it does not by itself establish a confirmed service-wide outage or its cause.
Read more →A maintenance window is a planned period reserved for work on a system or service. The actual notice should explain the affected functions and expected timing without treating every nearby issue as related. Planned work can have different impacts from an unplanned outage, and completion should be reported through the service's normal communication process when information becomes available.
Read more →An incident update communicates the currently known state of a service problem. A useful update distinguishes confirmed impact, work in progress and information still unknown. It should describe its scope and time clearly, avoid unsupported causes or restoration promises, and be revised when the responsible team has material information about the incident being handled.
Read more →Escalation moves an unresolved issue to a person or team with the relevant authority, expertise or access. It is most useful when earlier observations, safe checks and outstanding questions are recorded clearly. Escalating does not itself identify the cause or guarantee a fixed response time; the next step depends on the actual service process and issue scope.
Read more →A root cause is an underlying reason that meaningfully explains an observed failure and guides prevention or correction. It is different from the first visible symptom or a convenient guess. Establishing it can require comparisons, logs and operational evidence, especially when several independent systems contribute to a viewing setup or account workflow at the same time.
Read more →A change history records relevant modifications over time, including what changed, when and why. It helps connect new behaviour with updates or configuration changes without assuming that events close together have a causal relationship. Keeping versions and previous settings available also makes controlled comparisons and appropriate reversals easier during troubleshooting or routine account operations.
Read more →LET’S GET YOU STARTED
Install a suitable player, then WhatsApp us for your 24-hour trial.