Product:
Category:

February

Here is the new release of Flussonic Media Server 24.03! Now with SRT support per stream in Admin UI, configuring SRT ports is much more intuitive and convenient, LL-HLS and HLS fMP4 playback is now available in Safari browser, and thanks to OpenMetrics integration into Reference API, managing Flussonic monitoring with Prometheus has become more efficient. Plus, there’s now an HTTP metrics dashboard in your Client Area, and a camera preview before joining a call at demo.flussonic.com. And that’s not all - in this release we have worked hard on other features, improvements and fixes to improve system stability and make our users happier!:)

Media Server Documentation

Client Area

New

  • #20697 (Flussonic) Refactored the cluster logics to use Streaming API. This allows servers to avoid full authorization among themselves and provide only the data that is necessary for the operation of the cluster.
  • #32950 (UI) SRT ports per stream configuration is now available in the UI as it is the preferrable way of configuring SRT supported by most clients.
  • #35096 (Flussonic) Added the support for AC-3 audio signalling in multiplexer. This is required for feeding the signal to ATSC QAM networks.
  • #35683 (Flussonic) Improved the WebRTC publishing procedure to avoid handshake_timeout at DTLS handshake.
  • #36337 (Flussonic) Supported the LL-HLS and HLS fMP4 playback in Safari browser for WebRTC-published streams. This is useful for distribution of a content published by contributors from their browsers to a wider audience.
  • #36606 (Flussonic) Supported FairPlay encryption of HLS HEVC fMP4 streams for VOD playback.
  • #36810 (Flussonic API) The API Reference now shows the OpenMetrics names corresponding to the API parameters. This facilitates the configuration of Flussonic monitoring with Prometheus.
  • #36921 (DVR Player) The screenshot button is now available not only in the archive but also when watching live video.
  • #37329 (DVR Player) Added the support for DVR Player localization.
  • #37804 (Flussonic) The default settings for LL-HLS were adjusted for playback on iOS devices.
  • #37609 The documentation for Flussonic Watcher is now available separately from Flussonic Media Server but at the same flussonic.com/doc domain. Use the “Flussonic Manual” section in the main menu (on the left) to switch between Watcher and Media Server documentation.
  • #31551 Added the ability to sort streams by view time or traffic in the Statistics - Sessions - Streams tab at my.flussonic.com. This will help you find the most popular or unpopular channels.
  • #36419 Added the HTTP metrics dashboard at my.flussonic.com giving you insight into how your streams are played via HTTP based protocols to troubleshoot any issues.

Improved

  • #26949 (Flussonic API) Improved the auth backend API schema description to distinguish publish requests authorization.
  • #34130 (Flussonic) Improved the indexation of Flussonic RAID to try finding a blob when path to it became undefined for some reason.
  • #34131 (Flussonic) Improved the Flussonic RAID cleanup process to avoid the situations when blobs cannot be removed.
  • #36216 (Flussonic) Improved the DVR cleaning when using Amazon S3 cloud storage to support batch deletion which reduces the number of requests.
  • #36223 (WebRTC Player) Updated the readme to clarify that you should call screenShare() both to start and stop screen casting.
  • #36341 (DVR Player) Improved the Player for more traffic saving: when the tab with Player is inactive for 30 seconds, playback stops until restarted manually.
  • #36908 (DVR Player) The Player now uses relevant Watcher API v3 to fetch episodes.
  • #37515 (Flussonic) Added the /opt/flussonic/contrib/dvbscan.erl CLI tool for debugging DVB adapters.
  • #36088 Updated the instructions on streaming files from cloud to provide a step-by-step setting procedure.
  • #36451 Updated the DRM config examples to use relevant resource_id instead of obsolete meta drm_id.
  • #37005 Updated the SRT protocol page with more details on the protocol features and our implementation.
  • #37600 Updated the article about streaming from cloud to include config example.
  • #37672 Added the description of HTTP metrics tab in Retroview.
  • #36580 Improved the navigation through ticket messages at my.flussonic.com to show the last message right away when opening the ticket.
  • #36791 Implemented a preview of the publication before joining a call at demo.flussonic.com so that you don’t accidentally join with the camera on if you don’t want it.

Fixed

  • #15166 (Flussonic) Fixed the issue with HLS ingest interrupting when SCTE markers are encountered in the input stream.
  • #15909 (Flussonic) Fixed the necessity to set pixel=10 setting for reading teletext from SDI cards. This value is now default.
  • #24090 (Flussonic) Fixed the issue with SDI input not switched back when restored after a failure if a backup input was engaged.
  • #32007 (Flussonic API) Fixed the mixer status indication when one of the sources is down.
  • #35054 (UI) Fixed the issue with episode markers not displayed on the timeline when using the Player in Watcher Client UI (PWA).
  • #35604 (Flussonic) Fixed the issue with VOD files not played via DASH at certain combination of parameters in the source file.
  • #35986 (Flussonic) Fixed the issue with too long zap time (about 5 seconds) when receiving publications from Cisco CMS via RTMP.
  • #36180 (Flussonic) Fixed the incorrect play session counting.
  • #36181 (Flussonic API) Fixed the issue with gte filter returning not only the correctly filtered values but also null values for the requested field in the GET /streams request.
  • #36274 (Flussonic) Fixed the incorrect segment lengths for HLS or DASH output of a stream with M4S input when using track filter on the output.
  • #36283 (Flussonic) Fixed the issue with logo not overlayed in the embed.html player when some protocols were restricted with Only condition, even if only player restriction was added.
  • #36309 (Coder) Fixed the issue preventing the device firmware from being updated through the Chassis tab in the UI.
  • #36499 (Flussonic) Fixed the issue with SRT ingest failure when provider parameter was added in the stream config.
  • #36511 (UI) Fixed the issue with the “Restart” button not displayed after an update.
  • #37097 (UI) Fixed the issue with output bitrate not displayed in the “OUT:” field.
  • #37191 (Flussonic) Fixed the issue with RTMP push to rev.ai.
  • #37226 (Flussonic) Fixed the issue with SRT module crashing at Rendezvous Handshake.
  • #37282 (Flussonic) Fixed the issue with sound missing on the output from Flussonic because SR (Sender Request) message was not sent for audio tracks.
  • #37308 (Flussonic) Fixed the empty PMT in the MPTS after switching inputs which prevented the stream decoding.
  • #37355 (Flussonic) Fixed the issue with handling ack_read messages that may have caused stream hanging especially when publishing from Wirecast.
  • #37420 (UI) Fixed the issue with RTSP ingest tracks incorrectly passed from the UI to Media Server. You can now specify any number of tracks using comma as separator.
  • #37805 (Flussonic) Fixed the error of SRT decoder.
  • #37852 (UI) Fixed the error at multiplexor renaming.

With the new Flussonic Watcher 24.03 version, we present a number of improvements that significantly enhance the user experience and improve the security and usability of the system. Give your subscribers the ability to secure PIN pincode access to the mobile app. With a new feature in the Watcher Admin UI, you can easily send RTSP/HLS camera URLs via the Sharing tab. And that’s not all! Upgrade to version 24.03 and try our new features for yourself!

Watcher documentation

New

  • #33714 (Iris) Implemented the H.264, H.265 and JPEG codecs settings in Iris for cameras with SSC30К (YCX) chipset.
  • #34064 (UI) Added the ability to use PIN code for authorization in Watcher Client UI (PWA). Users can set the PIN when logging into the app or on the Security tab in their profile.
  • #35269 (UI) Added the ability to share camera RTSP/HLS URLs for using on other servers. The sharing tab is available in Watcher Admin UI.
  • #36104 (UI) Added the camera list page in Watcher Admin UI. All cameras are listed there but the video is not available to ensure privacy. This page is designed for troubleshooting the issues reported by your users.
  • #36460 (Iris) Implemented the auto day/night mode switching in Iris for cameras with SSC30К (YCX) chipset.
  • #36923 Designed the API for attendance report. It will help you find out who visited the premises during a specified time interval.
  • #35875 Added the article about how our video analytics solution may help you find records of unregistered visitors when investigating an incident on private facility.

Improved

  • #34067 (UI) Improved the Watcher Client UI (PWA) loading page to better indicate that the loading is in progress.
  • #34461 (UI) Improved the indication of HTTPS being required for push messages to be delivered.
  • #36811 Improved the stability of Watcher NVR status indication.
  • #37179 (UI) Added the Streamers page for managing streamers in Watcher Admin UI. There are more settings on the Streamers page than on Health page in Watcher UI.
  • #37220 Watcher can now tell the UI which pages are allowed to the users according to their permissions so that the UI could display or hide corresponding menu items.
  • #37243 Improved the Watcher installation script to avoid using curl as it may not be installed and use wget instead.
  • #37404 (Iris) The HAL module for cameras with SigmaStar SSC30К (YCX) chipset implemented as a separate binary file.
  • #34546 Added the instructions on installing video analytics.

Fixed

  • #32011 Fixed the issue with episodes of cameras unavailable to admin displayed on the Events tab in grey making it look like the system functions incorrectly. Only the episodes from permitted cameras are now displayed.
  • #33881 Fixed the crashes of Watcher Mobile app at launch.
  • #34179 Fixed the issue with events database not cleared according to the storage depth settings.
  • #34476 (UI) Fixed the issue with “back to live” button not shown when browsing the archive in Watcher UI.
  • #35000 (UI) Fixed the issue with output bitrate incorrectly displayed on the Health page. Please use the new Streamers page for monitoring the correct bitrate.
  • #36348 (UI) Fixed the issue with zero duration of an episode downloaded from the list of episodes in Watcher Client UI (PWA).
  • #36355 Fixed the issue with installation of Watcher on ARM64 architecture.
  • #36750 Eliminated the motion events duplicates.
  • #36828 Removed the false error message “Config external error while refresh” showed when the streamer status was actually OK.
  • #36856 (UI) Fixed some issues with localization in Watcher UI.
  • #37237 Fixed the issue with Central not starting when newly installing Watcher.
  • #37260 Fixed the issue with some subservices not restarting automatically when updating Watcher.
  • #37815 (UI) Fixed the issue with the “back” button in the camera viewing page returning to the previous episode instead of Cameras page.

Welcome to the release notes for Central 24.02, where we bring you enhanced control and monitoring capabilities for Central analytics, as well as other various improvements and bugs fixing.

New

  • #34906 Implemented the display of the number of online streams on analytics nodes.
  • #35516 Supported the layouting of streams with analytics enabled between analytics nodes only; failover and stream limits are also available.
  • #35827 The status and last_detection_at data are now collected for the streams with analytics to facilitate troubleshooting.

Improved

  • #35182 Improved the stream layouting to speed up stream allocation at the first launch or restart of Central by immediately launching the layouter.
  • #35811 Implemented liveness_probe and readiness_probe methods allowing you to check whether Central is started and ready to use. This is helpful when deploying your cluster in Kubernetes or other container orchestration system.
  • #36436 Added the ability to get stream.vision.stats from Central.
  • #36551 Improved the events filtering by camera name.
  • #36624 Added the ability to set the stream’s layout and the batch stream save operation for setting the layout for a bunch or all streams.

Fixed

  • #35993 Fixed the issue with streaming endpoint hostname not assigned to Agents.
  • #36494 Fixed the issue with NVR Agents resetting unexpectedly some time after activation.
  • #36547 Fixed the issue with stats for identification nodes not saved leading to the analytics events not shown.
  • #36616 Fixed the issue with the stream stats returned for disabled streams making them appear as online/alive. The stats are now cleared when disabling a stream.
  • #36760 Fixed the issue with streams allocated to analytics nodes while not being ingested on any streamer.
  • #36761 Fixed the issue with person previews not saved for persons created by the analytics module making it impossible for the user to identify the person.
  • #36832 Fixed the issue with Agent disconnections caused by the streampoint key resetting after streamer update.
  • #36843 Fixed HTTP 500 error when requesting the Agent update.
  • #36847 Fixed the issue with streams not allocated to streamers when created from Watcher.
  • #36849 Fixed the issue with episode previews not updated when the episode was updated by an analytics node which resulted in low quality of the preview in Central.
  • #36861 Fixed the issue with Central not returning stats for analytics nodes.
  • #37022 The Central’s environment variables now have the CENTRAL_ prefix.

January

We step into 2024 with a new version (24.01) of Flussonic Media Server. In the first changelog of the year we are thrilled to present our demos designed specifically for you to test the capabilities of our WebRTC for video meetings, SRT publishing with a dynamic port and a DVR Player. The demos are available at demo.flussonic.com.

And that’s not all! We also prepared a bunch of new features and improvements (as well as bugs fixed) in the freshest as the January frost version of Flussonic Media Server!

New

  • #15418 (DVR Player) Supported LL-HLS playback in embed.html. You can use ?realtime=true&proto=ll-hls query string to request it from the server.
  • #24926 (Flussonic) Implemented a framework for appliance firmware creation.
  • #26826 (Flussonic) Supported FairPlay encryption of HLS HEVC fMP4 streams for all DRM providers.
  • #32762 (Flussonic) Flussonic can now accept publications from Cisco CMS via RTMP.
  • #34074 (DVR Player) Finalized the implementation of the archive fragment downloading from DVR Player. You can check it out in the DVR Demo.
  • #35454 (Flussonic) Supported DVB subtitles conversion to WebVTT for SRT published streams.
  • #35517 (Flussonic) Added the ability to use several words divided by space in push or input descriptions.
  • #35576 (Flussonic) Implemented the ability of Flussonic Media Server to proxy requests to Central installed on the same server. This feature can be used in single-server Watcher installations.
  • #35623 (Flussonic) Our own SRT implementation (just like the previous one based on libsrt) supports key refresh which is important for long-time broadcasts.
  • #35706 (Flussonic) Added the config_external_success event indicating that the configuration backend is requested successfully.
  • #33203 The article about creating your own IPTV channel was updated with instructions on ad insertion.
  • #34899 Fixed the example of Prometheus configuration to include a more clear targets example.
  • #35155 Demo WebRTC call is available at demo.flussonic.com. It demonstrates the Flussonic WebRTC capabilities in a video chat room.
  • #35360 Added the demo of SRT publishing with dynamic port at demo.flussonic.com. The port changes every time you update the page. You can push your stream via SRT from OBS Studio, Larix Broadcaster, ffmpeg, Flussonic Media Server, etc. The stream instantly shows in the player.
  • #35733 Added the demo of DVR Player at demo.flussonic.com. You can watch live video and archive of a CCTV camera and download the archive fragments.

Improved

  • #33851 (WebRTC Player) Updated the readme for Flussonic WebRTC Player npm package to add missing descriptions of methods like screenShare() and options like start_track.
  • #34460 (Flussonic) Improved memory allocation to enhance general system performance.
  • #35062 (Flussonic) Improved the H.265 (HEVC) transcoding to optimize CPU utilization.
  • #35087 (UI) The cluster key is no longer required when creating a streamer in Central Admin UI because you don’t need the cluster key for video analytics streamer roles.
  • #35208 (Flussonic) Improved our Erlang SRT Listener to support single port for play and publish in the same way as in the libsrt implementation.
  • #35698 (Flussonic API) Improved the requests routing with config_external enabled to bypass internal HTTP requests.
  • #35727 (Flussonic) Fixed the issue with RTMP push restarting every time the source is disconnected by timeout with backup file configured.
  • #35778 (Flussonic) Improved the archive cleanup process to exclude unnecessary operations.
  • #35789 (UI) Updated the name of the inference streamer role in Central Admin UI to make in clear that it should be selected when vision-inference package is installed on the corresponding streamer.
  • #35865 (Flussonic API) Moved srt_port_resolve to stream stats.
  • #36006 (Flussonic) Fixed the issue with unnecessary information in logs about disabled playback protocols.
  • #29042 Added transcoder instructions to the [IPTV/OTT quick start] page.
  • #31371 Added the article about the use of firewall and why you don’t need it on servers with Flussonic.
  • #33753 The [Filtering collections] principle of Flussonic API design was updated to clarify that _is and _is_not filters are only applied for comparison with NULL.
  • #34116 Updated the MSE Player page to remove obsolete information about use without npm and synchronous playback of several DVRs at the same time.
  • #34627 Described the option for copying EIT with EPG from a specified source to MPTS.
  • #34655 Fixed the link to API on the SRT page, fixed the description of the latency parameter used for SRT input and SRT push.
  • #35289 Added the sentence about various disk size allowed in [Flussonic RAID for DVR](https://flussonic.com/doc/standby-mode-of-multicast-pusher/.
  • #35465 LL-HLS Playback instructions moved to the separate page and updated according the latest changes in the API and UI.

Fixed

  • #31284 (Flussonic) Fixed the issue with ad_splice insertion when passing SCTE-35 markers through Flussonic leading to creation of too short segments that caused bad_segment message in logs and too long buffering.
  • #31993 (Flussonic) Fixed the issue with SPTS streams duplication when standby is enabled.
  • #32827 (Flussonic) Fixed the issue with about one second part of the file cut when transcoding it with file_processor.
  • #33995 (Flussonic) Improved RTSP playback stability for VLC and some other players.
  • #34023 (Flussonic) Fixed the issue with server playlist crashing when reading some files with specific subtitle timings.
  • #34200 (Flussonic) Fixed the freeze before injected ads in segments with subtitles.
  • #34345 (DVR Player) Fixed the issue with DVR Player showing black screen instead of the archive in the Dashboard mode in Watcher UI.
  • #34672 (Flussonic API) Fixed the HTTP 500 error returned by openapi_handler when required fields were missing in select query string request.
  • #34715 (Flussonic) Fixed the issue with transcoder failing and not restarting properly after a specific minor source failure.
  • #34748 (Flussonic) Fixed the issue with the actual ASI output bitrate being eight times higher than specified in the config.
  • #34820 (DVR Player) Fixed the issue with fast playback not starting without changing playback position on the timeline in Safari at iOS 17.1.1.
  • #34910 (Flussonic) Fixed the issue with Media Info changes causing stream restart.
  • #35084 (DVR Player) Fixed the issue with playback freezes in Chrome when selecting points on the timeline one after another.
  • #35109 (Flussonic API) Fixed the HTTP 500 error returned in response to PUT /transponders/{name} when PID bitrate is higher than multiplexer bitrate. HTTP 400 with pid_bitrate_higher_than_transponder_bitrate message is now returned instead.
  • #35231 (Flussonic) Fixed the issue with On-demand stream not starting when requesting its playback via RTSP.
  • #35305 (Flussonic) Fixed the issue with too often update checks causing excessive CPU load on the server.
  • #35345 (Flussonic) Fixed the issue with Media Server requesting the list of episodes from Central in a wrong way and being unable to delete the expired episodes recording as a result.
  • #35361 (Flussonic) Fixed the issue with update not performed from the UI.
  • #35383 (WebRTC Player) Fixed the issue with native controls in WebRTC Player not disabled by default and interfering with custom controls.
  • #35444 (Flussonic) Fixed the issue with exporting more than hour-long archive to an MP4 file on the server disk via the API interrupted by a timeout.
  • #35547 (Flussonic) Fixed the inconclusive error messages in logs indicating that IPTV plugin is not enabled or configured.
  • #35565 (DVR Player) Fixed the inability to scale and hover over the frame when the stream is paused.
  • #35691 (Flussonic) Fixed HTTP 500 error appeared when playing DVR from Amazon S3 over segment-based protocols when copying is configured and the segments that are not yet in memory are requested.
  • #35705 (Flussonic) Fixed the issue with archive cleaner reporting in logs about inability to delete already deleted archive blobs.
  • #35863 (DVR Player) Fixed the issue with numbers cropped in the archive fragment selection box.
  • #35876 (DVR Player) Fixed the issue with the “play” button displayed instead of “pause” when autoplay is enabled.
  • #35959 (Flussonic) Fixed the issue with SHOUTcast crashes leading to session interruptions.
  • #35566 Fixed the issue with main page my.flussonic.com opening instead of specific ticket when tapping a push message about a new answer in the ticket.

Watcher version 24.01 introduces innovative features, including a refined timeline scale, streamlined video analytics configuration, the addition of a DVR Player for easy archive fragment selection and download, and the implementation of proxying requests to Central, marking a significant step towards enhanced scalability and resource optimization.

Try out the new features, improvements and bugs fixed, and witness the evolution of Watcher.

New

  • #35048 (UI) The timeline scale increased to show records for the last hour by default facilitating the archive navigation.
  • #33206 timelapse option is enabled for watcher ui users.

Improved

  • #31964 (UI) Deleted the “Vision” setting from streamer profile in Watcher UI. The relevant way of configuring the video analytics will be available in our documentation as soon as possible.
  • #35694 Supported the routing of API requests with /central prefix to Central.

Fixed

  • #30906 (UI) Fixed the issue with filtering on the Events page in Watcher UI resulted in emptying the Events page.
  • #33670 Fixed the issue with unrecognized persons not appearing in the event list and in the Lists of Persons.
  • #34121 Fixed the issue with two or three push notifications on one event in Watcher Client UI (PWA).
  • #34687 Fixed the issue with branding logo applying only after clearing the cache.
  • #34986 (UI) Fixed the display of events and player controls on the camera page of Watcher Client UI (PWA) when viewed in landscape orientation on mobile devices.
  • #35466 (UI) Fixed the issue with NVR cameras not played in the DVR Player when listed on a second or greater page in the camera list in Watcher UI.
  • #35601 Fixed the issue with Watcher not being able to connect with a camera via ONVIF when the camera responded with a minimum GetNTP response.
  • #35967 Fixed HTTP 400 error returned in response to GET /persons when persons in the old format were present in the database.

Flussonic Central 24.01 is an update, featuring Long Polling for faster episode delivery, streamlined camera connection with Assigning Agents, enhanced scalability through streamlined streamer deployment, optimized face fingerprint handling, improved distribution of episodes for superior video analytics tasks and many more. Explore the new possibilities of Flussonic Central in the freshest release notes 24.01.

New

  • #31270 Enhanced the delivery of episodes to Watcher or other client application by using the Long Polling technique. This will help decrease the delay when using episodes for access control like opening door by a recognized face or opening gates by a recognized license plate.
  • #35196 Assigning Agent with a streampoint is made independable from the layouter to allow the camera connection even if the layouter is unavailable.
  • #35671 Supported the /central/api/v3/ API path along with the /streamer/api/v3/ to distinguish the services installed on the same server without configuring different ports.
  • #35918 Implemented the storing of updated_at in the Central’s database to avoid possible desynchronization and episode loss.
  • #36132 Added the ability to disable provisioning of configuration from Central to streamers. It is useful when you deploy your streamers in Kubernetes or other orchestration system. Set CLUSTER_NODE_CONFIG_PROVISION_ENABLED = false to use this feature.

Improved

  • #35259 Improved the distribution of episodes between the analytics nodes to allow Central push episodes batches for identification. This increases control over the results of episodes processing on the analytics nodes and provideы means for handling any errors that may be encountered during the episodes processing.
  • #35377 Improved the check for episode validity to forbid episodes with updated_at=0 and started_at=0 because such values do not make sense and may prevent validation by other services.
  • #35395 Improved the face fingerprint handling in Central to exclude merging data and utilize only the relevant data returned by the analytics nodes. This improvement increases the system performance.
  • #35402 Improved the validation of returned person list to exclude persons with invalid photos.
  • #35515 Renamed the name parameter to media to avoid confusion and highlight that the parameter has the same meaning as in GET /episodes.
  • #35597 Improved the episodes fetching from Vision Inference by implementing the polling technique to reduce the delay between the episode start and its appearance in Central.
  • #35617 Renamed vision role to inference to reflect that this role corresponds to vision-inference package.
  • #35696 Updated the config_external and central_event_collector URLs to use /central prefix instead of /streamer.
  • #36008 Default HTTP timeouts increased up to 60 seconds to improve Central operation in Watcher software package.
  • #36009 Removed the event sinks enabled/disabled setting because there is no need in disabling it.
  • #36040 Increased the system security by removing the password and API key generation when installing Central as part of Watcher software package. The users shall set the password themselves in order to use Central Admin UI.
  • #36044 Removed the SINGLE_INSTALLATION config parameter to facilitate scaling.
  • #36154 Central’s default port is now 9019.

Fixed

  • #35249 Fixed the issue with GET /episodes request with filter by updated_at returning not all the detections present in the database because the updated_at value was processed by Central in a wrong way.
  • #35265 Fixed the issue with streams moved to another streamer at failover not returning to the streamer specified in their settings after that streamer has restored after failure.
  • #35501 Fixed the issue with Central continuing to provision a stream to analytics nodes after vision is disabled on the stream.
  • #35571 Fixed the issue with updated_atsynchronization ensuring its uniqueness for every episode.
  • #35610 Fixed the issue with updated_at value not updated for the episodes received from the analytics nodes.
  • #35684 Fixed the issue with the streams having vision enabled not allocated to inference nodes.
  • #35922 Fixed the issue with scheme parameter not applied when executing GET /streams request.
  • #35923 Fixed the issue with analytics not working if cluster_key is not specified in Central which is wrong because cluster_key is not required for analytics nodes.
  • #36026 Fixed the issue with Agent statuses incorrectly probed by Central leading to incorrect expectations of the Agent allocation to streamers.