ZEN MASTER December 2022 RELEASE NOTES

the following updates will be included in the zen master december 12, 2022 release features the following new features were implemented in this release • intelligent data platform – multi object correlation analysis (idp moca) in this release idp now automatically detects incidents comprised of multiple objects – sources, targets, and broadcasters – and determines a root cause idp uses correlation analysis to determine the common factor in a set of errors across multiple objects that occur within a few minutes of each other to help operators and broadcast engineers see the root cause immediately, and with the most relevant supporting evidence key features • expanded blast radius – now you can see all the objects that had an error at the same time and what relates them, even if they span multiple channels, all grouped together in a single incident • automated rca attribution – incident descriptions now include the common factor across all related errors, which can be the client side network (of the sources and targets), the server side network (of the broadcaster), or the broadcaster it also shows the most relevant metrics for the incident in the default incident view • customizable rca report – while the default incident view shows the root cause and most relevant graphs, users can also add other graphs and notes to the report, change the time range, and export the report to share with other team members auto install agentz by enabling “install agentz automatically”, zen master will automatically install agentz on any existing and future broadcasters connected to the cluster the feature is off by default note that due to agentz installation requiring a restart, zen master will not auto install agentz on a broadcaster that already contains any inputs to avoid disturbing active streams the option to enable is located in the advanced section of the cluster • pull targets that are unable to connect now display a more informative message there are various reasons why a pull target may not connect to the serving broadcaster within a cluster more specific detail is now provided in the event of a failure, including a distinction where the issue is on dns redirection, connection to the actual broadcaster, etc • added support for rtmp targets on medialive channels • frozen & blank video detection thresholds can now be controlled and reduced to 10 seconds by default the detection window sizes for frozen video and blank video are a broadcaster input property and configuration is available in the advanced section of the zixi source • added support for mediaconnect entitlement targets the new target type can be found under the standard new target list, and provides the standard parameter fields expected by aws mediaconnect entitlements additional improvements and changes the following additional improvements and changes were implemented in this release • added option to propagate zen master tags to s3/mediastore on hls targets • added option to clone mediaconnect flows without transferring the source to the new flow this is now the default behavior • added prefer primary/backup source to zixi pull targets • added option to remove nulls and sdt in pid mapping profiles • added a preserve rtp headers option on udp/rpt sources • added more max bitrate options to udp/rtp sources • added more detailed alerts on performance related transcoding errors • improved target error messages when error is caused by source auto pull • mediaconnect/medialive errors on user actions are now logged in the zen master events log • email notifications now explain which role caused the email to be sent to the user • http targets will now report more detailed error when possible • zixi pull targets now display their current client ip on the details page • stream info now shows gop and frame duration information • broadcaster restarts are now logged regardless of reason • source/channel failovers are now logged • source reconnection event log now mentions which broadcasters are involved in the event • improved aws cluster implementation with better logging and reusing existing zen master broadcaster id when an instance is replaced by aws • error count labels on the left hand main menu are now clickable and link to the relevant page with a filter to show the objects that are in an error state • added option to revert new list tables to default configuration • auto rows are now back with a vengeance in new list tables + added an upper limit on number of rows • cluster authentication monitoring is now consistent across all authentication modes • restart confirmation now uses only backend logic preventing incorrect or missing restart prompts on edit • mediaconnect/medialive monitoring now scales to any number of flows/channels • ui polish api • using invalid ids in api calls will now return an error with a 404 http code bug fixes the following issues were resolved • event log report now contains all expected results • fixed incorrect mediaconnect srt target status on dashboard • fixed issue causing zixi pull targets to get stuck on an offline source when a working one is available in some scenarios • fixed rare issue causing zen master to report an offline error on zixi pull targets when they are working • failover sources should now recover on all component source changes/reconnections • http targets no longer allow deleting chunks in dvr mode • fixed automation tasks getting stuck in executing state • non admin users can now switch channels • fixed issue causing channels to save in a broken state when changing the channels cluster without manually updating the target broadcaster field • creating an incident from the event log will now have a more reasonable default start/end time • fixed updating adaptive channel component sources not propagating to broadcaster • fixed kafka test showing generic error message with no details • auto pulls are no longer created when disabled or not needed • updated failover rules ui to be more understandable • clarified dtls note on clusters form • fixed multiple issues with targets on grids e g missing name/link to details page • fixed webrtc playback on sources with multiple audios • fixed multi edit of target tags hanging forever in some cases • fixed spin up of broadcaster on azure broadcaster failing displaying a generic error while the vm is successfully created • correct smoothing configuration now applied to transcoded source in cbr mode • daylight savings time will no longer cause automation tasks to run an hour early/late • fixed an issue causing some scte 35 messages to not get logged