STB playout
The STB Playout report lists all the successful playout requests from STB users. There is one entry per playout type (Vod, Live, or NPVR). The reporting period is end-user selectable.
Availability
This report is available where all of the following module versions (or later) are present:
- LKR: 2.8.4
- UAV: 1.1.6 (provides userUID support for authorisation checks at the API level).
- CDG: 1.1.12 (requires full metadata transfer from CDG to UAV).
Report columns
Column name | Description |
|---|---|
| day | The day on which the playout request was made. |
| accountId | The STB user's account ID. |
| key | The contentId of the content being played out. |
| timestamp | The timestamp of the request. |
| value | Whether the playout was successful. |
| genre | The genre of the content. |
| contentType | The type of the content (one of BTV, Live, or NPVR). |
| devicename | The name of the device. |
| contentTitile | The title of the content played out. |
| userId | The ID of the user making the request. |
Input parameters for report generation
Parameter | Type | Description |
|---|---|---|
| Lower date threshold of report period | DateTime | Start Date for the report, including the specified value. |
| Upper threshold of report period | DateTime | End Date for the report, including the specified value. |
Data extraction files
The data extraction files can be found in the "/opt/npvrlocker/reporting/bsm/etl" directory. The following file is used for this report:
Extraction file | Summary | Notes | Query |
|---|---|---|---|
| npvr-activity-notifications-uav.ktr | Transforms data from the UAV cassandra database to the reporting Mongo database to support activity type reports directly in BSM's "uav_activity_notifications" collection. | Data in the UAV activity_notifications collection is timestamped to expire after a specified period. This extraction will retrieve all the data and insert it into the BSM reporting MongoDB, thereby eliminating duplication, and enabling the system to take only the latest data from UAV, rather than replacing the MongoDB collection with a full copy every time the extraction is run. | SELECT * FROM activity_notifications |
BIRT design template file
File name | Summary | Reports collection | Query |
|---|---|---|---|
| STBPlayoutReport.rptdesign | STB Playout Reports | uav_activity_notifications | { "collectionName" : "findQueryExpr" : {"uav_activity_notifications", {name: 'watch', deviceid: 'STB', value: 'Success'}}} |
Sample report
The following image shows an example of an STB Playout report:
