WCS sends the following stream parameters for aquisition:
Metric | Id | Description |
VIDEO_HEIGHT | 2 | Высота видео |
VIDEO_WIDTH | 3 | Ширина видео |
VIDEO_RATE | 4 | Битрейт видео |
VIDEO_SYNC | 5 | Синхронизация видео |
VIDEO_FPS | 6 | Частота кадров видео |
VIDEO_NACK | 7 | Количество NACK-запросов |
VIDEO_PLI | 8 | Количество PLI-пакетов |
VIDEO_CODEC | 9 | Видеокодек |
AUDIO_SYNC | 10 | Синхронизация аудио |
AUDIO_RATE | 11 | Битрейт аудио |
AUDIO_LOST | 12 | Количество потерянных пакетов аудио |
AUDIO_CODEC | 13 | Аудиокодек |
The available metrics list can be obtained using REST API query /api/metric/list
https://hostname:8090/api/metric/list { "id": "4" } |
Where:
If metric Id is set, the response will contain information about the metric with this Id only. In other case, response will contain all the metrics list.
The response contains the following fields:
[ { "id": 4, "name": "Video rate", "note": "", "enumName": "VIDEO_RATE" } ] |
Metrics are combined to profiles to collect from specific nodes. Every profile contains specific metrics set and aquisition rate. A couple of metric aquisition rules can be set for certain profile which are applied to stream on node.
A number of profiles can be applied to one node (WCS instance). In this case, metric sets and rules from profiles are summarized, and minimum aquisition rate for same metric is applied. Let's look to the example:
1. The profiles profile1 and profile2 are applied to test1.flasphoner.com node
2. profile1 includes:
Stream name == stream1
3. profile2 includes:
Stream name == stream1
As a result, for the stream stream1 on test1.flashphoner.com node the following metric sets will be aquired: