Flussonic Central 23.06

Introducing the highly anticipated 1st official release of Flussonic Central, packed with exciting enhancements! Delight in the complete separation of streamer control functions from Watcher VMS. Empower your system with Agent provisioning, authorization, and monitoring. Witness automatic stream return and seamless switching between streamers. Expand your hardware compatibility with multiarch installation packages. Optimize resource allocation using intelligent stream distribution with cluster snapshots. Effortlessly deploy within Docker containers. Simplify configuration updates through automatic config_external provisioning. Elevate your streaming infrastructure with Flussonic Central’s streamlined and efficient configuration management. Explore a host of other improvements and updates that elevate your streaming experience to new heights.

Flussonic Central (23.06)

• #30303 (new) Supported cursors for streams_list and streamer_streams_list Central API requests.
• #30392 (new) Implemented retries when polling streamer statuses and getting HTTP 400 or 500 errors to avoid false offline statuses.
• #30393 (new) Added the STREAMER_FETCH_TIMEOUT environment variable allowing you to set up timeout for requests from Central to Media Server.
• #30478 (new) Disabled streams are not provisioned from Central to Media Server any more.
• #30481 (new) Added logging for JSON body of HTTP API requests.
• #30523 (new) Added DATABASE_CONNECT_MAX_RETRIES and DATABASE_CONNECT_RETRY_TIMEOUT environment variables allowing you to set up the number of retries (default 20) and timeout (default 1 second) for Central to connect with its database.
• #30525 (new) Improved logging of the Agent connection process to facilitate troubleshooting when Agent does not connect.
• #30793 (new) The mechanism for distributing streams among streamers has been optimized: instead of making a decision for each separate stream and streamer, a snapshot of cluster is now collected for all streamers at once to define online and offline streamers; then a decision is made to reassign the streams based on the snapshot.
• #30809 (new) The config_external provisioning from Central to streamers implemented for installations without Watcher (when UPSTREAM_URL is not specified).
• #30815 (new) HTTP requests from config_external are now logged only on debug log level. Use the LOG_LEVEL variable to configure logging; supported values are “debug”, “info”, “warn”, “error” (default), and “fatal”.
• #30265 (fixed) Fixed the issue with query parameters not forwarded when redirecting requests from Central to a specific streamer.
• #30318 (improved) Fixed the issue with peer_ip in GET /streamer/api/v3/agents returned in host:port format although API schema suggested it to be in standard IPv4 format.
• #30319 (improved) Added a connection check for Agents; the polling stops if there is no connection.
• #30363 (improved) Fixed the issue with Agent statuses displayed in Watcher UI as disconnected even though the Agents were online.
• #30381 (fixed) Fixed the issue with streamer polling continuing after deletion of the streamer and the deleted streamer remaining in the effective_streamer_hostname for some streams which also caused streamer status to be falsely displayed as online.
• #30382 (improved) Improved the process of provisioning configuration from Central to streamers to update all config by one PUT request instead of separate requests for each changed parameter.
• #30428 (improved) Fixed the issue with active camera becoming offline after switching from one streamer to another.
• #30455 (improved) Supported seamless archive for streamers under Central’s control.
• #30484 (improved) Improved the indication of configuration mismatch between a streamer and Central in Central’s log.
• #30489 (fixed) Disabled rproxy streampointkey provisioning for Central installations with Watcher.
• #30513 (improved) Fixed the issue with provisioning of updated streams from Watcher to Central and further to Media Server when old stream config was provisioned.
• #30543 (improved) Supported multiarch installation package for Central.
• #30549 (improved) Stream stats were removed from the config_external API.
• #30583 (improved) fix config file that was checked on installation
• #30662 (fixed) Fixed the issue with Central not starting in Docker if STREAMER_FETCH_TIMEOUT was not specified.
• #30684 (improved) The format of the config file unified to support bash-style KEY=value format.
• #30721 (fixed) Fixed the issue with streamer hostname not saved in DVR logs when changed.
• #30734 (fixed) Fixed the memory error appeared when removing a camera with Agent connected via Central.
• #30759 (improved) The effective_streamers_log table renamed to stream_dvr_history to better reflect its content.
• #30761 (fixed) Fixed the issue with existing camera settings not saved showing HTTP 500 error in Watcher VMS UI.
• #30763 (fixed) Fixed the issue with some cameras not returning to online status after Central restart.
• #30840 (improved) The messages about cameras’ streamers being not alive are now logged only on debug log level. Use the LOG_LEVEL variable to configure logging; supported values are “debug”, “info”, “warn”, “error” (default), and “fatal”.
• #30892 (fixed) Supported the name query string parameter in the GET /streams API request allowing you to filter requested streams.
• #30899 (improved) Added the LOG_REQUESTS configuration option allowing you to completely disable the logging of HTTP requests regardless of the log level.
• #30917 (fixed) DVR selection for the stream is temporarily disabled in the UI because DVR config is hardcoded for now. We will return the setting when DVR features are implemented properly. You can also set UI_DVR_ENABLED=true in the config to enable the field, but only one option (central) will be available for selection.
• #30922 (fixed) Fixed the issue with logging effective streamer hostnames. Only the change of the effective streamer is now logged.
• #30958 (improved) Some endpoints of Central API for working with DVR, authorization, events, PTZ, and video analytics made private (hidden) because they are not implemented yet. We will return them to the public schema as soon as they can be used.
• #30966 (improved) Improved the process of streamer polling: added timeout between the requests to avoid falsely identifying the streamer as disabled.
• #31079 (fixed) Fixed the issue with incorrect definition of an effective streamer for a stream when the stream without inputs remained on some streamer after failover to keep seamless archive.

Flussonic Central (23.05) 2023-06-02

• #24744 (new) Flussonic Central streamer control functions are now completely separated from Watcher VMS.
• #25897 (new) Supported Agent provisioning, authorization and monitoring via Flussonic Central.
• #29269 (new) The stream is now attempted to be returned to the streamer_hostname (if it is specified) after the streamer failure and switch to some other streamer.
• #29723 (new) The hostname and port are now checked when adding streamers to forbid adding the same streamer several times.
• #29736 (new) You can now filter the list of streams returned for the specific streamer by their name, for example: GET /streamers/{hostname}/streams?name=stream1,stream2,stream3. Such a request returns only the streams you specify if they exist in the config.
• #29748 (new) Eliminated the ambiguousness when setting different streamer names in the URI and in the body of the PUT streamers/{name} request: the name from the URI is applied and placed to the body automatically.
• #29757 (new) Agent stats are now stored in the runtime instead of the database to enhance the system performance.
• #29778 (new) Supported load balancer URLs for Flussonic Central.
• #29835 (new) The effective streamer where the stream currently runs is now returned in the running_on parameter of the GET /streams/{name} request and displayed in the UI.
• #29917 (new) Supported load balancer URLs for MSS protocol.
• #29920 (new) Single installation mode supported for Flussonic Central to allow operation when Central, Watcher VMS, and Media Server are all installed on the same host.
• #29950 (new) The GET streamers/streams request now returns HTTP 404 if the streamer hostname is not found.
• #30037 (new) Default API URL for a streamer is now the streamer’s hostname.
• #30051 (new) Supported provisioning of event_sink configuration from Flussonic Central to streamers.
• #30278 (new) Supported the cursor logics for stream fetching API.
• #29709 (improved) Flussonic Central now provisions and updates config_external on the streamers when API key is updated on Central.
• #29759 (fixed) The streamer hostname is now used instead of streamer name in all Central API calls for streamers.
• #29820 (fixed) Fixed the issue with auth settings not displayed in the Central Admin UI even though they were present in config_on_disk and active.
• #29831 (improved) Running without the config file is supported with all required configuration set in the environment variables to allow the use of Flussonic Central in Docker or other containers.
• #29842 (improved) The multiarch build of Central added to the Central Docker container to support ARM64 architecture.
• #29885 (fixed) Fixed the issue with authorization settings not removed from the config file when deleted in the UI.
• #29887 (improved) Stream stats are now stored in the runtime instead of the database to enhance the system performance.
• #29912 (fixed) Supported nullable fields in the PUT /streamers/{hostname} request.
• #29978 (fixed) Supported streamer hostnames with port specified.
• #29998 (improved) Updated the Agent interaction logics to update the streampoint only when the Agent is to be connected to a new streamer.
• #29999 (improved) Added the response to ping from the Agent and regular ping from Central to the Agent to monitor the connection.
• #30024 (improved) You can now get the streams configuration on a specific streamer using the GET streamers/{hostname}/streams API call.
• #30123 (fixed) Fixed the issue with a stream not switching from an explicitly specified streamer to a backup one in case of failure of the specified streamer.
• #30138 (improved) Flussonic Central now changes the streamers config only if it is different from what is configured on Central.
• #30140 (improved) The API_URL environment variable (instead of HOSTNAME as before) should now be used for setting the hostname and port under which Central is accessible by Flussonic for CONFIG_EXTERNAL + http_proxy requests.
• #30201 (fixed) Fixed the issue with external_config URL generation based on Central’s API_URL.
• #30233 (improved) Streamer stats are now stored in the runtime instead of the database to enhance the system performance.
• #30294 (improved) The Central initial config with which it starts is now saved in logs for debug purposes.
• #30309 (fixed) Data on the stream’s effective_streamer_hostname is now taken from memory during Central operation; the database is accessed only when the streamer changes.
• #30317 (improved) Fixed the issue with Agent ID not populated to the Central’s database for streams with Agents preventing the Agents from proper connection.
• #30343 (fixed) Fixed the issue with event subscriptions incorrectly provisioned from Central to Media Server preventing Watcher VMS from getting ONVIF motion detection events. Flussonic Central (23.04) 2023-06-02
• #29408 (fixed) Flussonic Central UI is now available at http://CENTRAL-IP as well as at http://CENTRAL-IP/admin