Actively sync SRS state #2

Closed
opened 2024-02-25 23:18:14 +01:00 by thunfisch · 0 comments
Owner

Current state for stream is passively tracked through connect/disconnect webhooks by SRS. If we miss a webhook for whatever reason, the state can become out of sync and need manual adjustment. This is a bit fragile.

Let's move over to actively scraping the SRS API for all nodes, and use that to keep track of streams.

Solution should scrape each SRS API in a short interval, and save the state ideally in-memory (e.g. using the available Redis KVS). Changes to the in-memory state should trigger re-evaluations of any configuration rules to spawn/remove Tasks.

Current state for stream is passively tracked through connect/disconnect webhooks by SRS. If we miss a webhook for whatever reason, the state can become out of sync and need manual adjustment. This is a bit fragile. Let's move over to actively scraping the SRS API for all nodes, and use that to keep track of streams. Solution should scrape each SRS API in a short interval, and save the state ideally in-memory (e.g. using the available Redis KVS). Changes to the in-memory state should trigger re-evaluations of any configuration rules to spawn/remove Tasks.
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cwtv/portier#2
No description provided.