Telemetry for capture module #73
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a work in progress (draft pull request)
Implements "telemetry" module so external applications can retrieve data from current capture session without disturbing it.
The data can be used by a monitoring application to generate statistics and also detect failures. As example, it could detect last frame block was processed a long time ago, so capture is stuck and action is required.
command:
output:
{ "status": "capturing", "fps_expected": 25.0, "fps_estimated": 19.7, "block_frames": 256, "dropped_frames": 85, "frame_time_average": 0.049, "capture_start_time": "2021-05-18T06:12:44.820058", "last_frame_block": "2021-05-18T06:13:28.868691" }TODO wish list: