ZEN MASTER June 2023 RELEASE NOTES

the following updates will be included in the zen master june 13, 2023 release features the following new features were implemented in this release • idp moca auto incidents in this release we have made a major update to idp multi object correlation analysis (moca) to auto generate incidents based on any errors observed by zen master, not just unrecovered packets incidents provide a roll up of errors when they become particularly significant so you can see outages in a single view with context to help you understand what’s going on and how to fix it, and to reduce the noise of low level alerts on the left side is the list of affected objects on the right, the root cause is at the top and related measurement graphs are listed below the description of the incident shows some root cause details including the shared resource and the incident type • incident definition and thresholds incidents are reported when there are 3 or more sources or targets having errors at the same time that share a common resource, and when at least 50% of the objects that share that resource are experiencing errors at the same time errors that happen on these objects within 10 minutes of a previous error are grouped together into the incident it is possible to have multiple related incidents if there is a period of more than 10 minutes without any errors in some cases, if there are multiple shared resources the system may also report multiple related incident records • shared resources \ client network – the network where source or target objects are connected networks are identified by network asn (autonomous system number), country code, and region code for example, us oh 123 is a network in ohio in the united states with asn 123 \ server network – the network where a broadcaster is connected \ network path – the connection between a source and a broadcaster \ broadcaster – the shared zixi broadcaster • types incidents can be of type network error or object error object error incidents can be triggered by a tr101 cc error on a source, or a broadcaster max cpu error, or any error reported in zen master • root cause, blast radius the root cause description for an auto generated incident includes the incident type, the shared resource, and some details about how many objects that share the shared resource (a network path, for example) are involved in the incident (sometimes called “impact” or “blast radius”) compared to the total number of objects connected examples \ client network error 57% of sources (8/14) on network us oh 123 have network errors \ object warning – network path 67% of targets (4/6) on network path (us oh 123 us ca 456) have object errors in incident view, object error incident records show the relevant errors for the selected time period for all related objects, as well as network and other measurement graphs • table view for grids the zen master grid screen now allows the user to toggle between the standard grid view, and a list view using the new tables architecture to toggle the view, choose the list icon from the view icon pair above the grid with the new view selected the user gains all the additional filter controls available in standard tables, as well as the displayed / hidden column controls and the ability to generate a quick report • broadcaster customization is now available on azure and gcp clusters already supported for zen master managed aws scaling clusters, customization of a broadcaster’s name and private / streaming ip settings is now supported for clusters launched in both azure and gcp this can be configured in the create new broadcaster dialog when selecting ‘add broadcaster’ in the cluster details section, or via the zen master api • agentz is now available for manual installation without causing a broadcaster restart whilst the agentz telemetry gathering tool can still be installed from zen master, it can now also be installed manually on a broadcaster unlike the zen master install, the manual install does not force a broadcaster restart the manual agentz installer can be downloaded from the zixi customer portal, and instructions are provided in the zixi agentz user guide • user management security notifications a new “account management” log object is introduced to log, track, and search for updates and changes to security objects including \ users \ groups \ roles these log entries are available for admin user only, and can be searched for in the event log filter all admin users will receive specific account management email notifications for changes to any security objects in the zen master environment if needed, admin users can opt out of receiving these emails in the ‘my account’ section • improved support and useability for aws elastic ip’s when using elastic ips for aws scaling clusters, zen master now introduces an option to prevent instances from launching if there are no more designated eip’s available the option, included in the cluster advanced configuration settings, will explicitly prevent aws from launching a new instance when no further elastic ip addresses are available, to guard against a cluster adding a broadcaster with an unknown public ip address regardless, the cluster now displays available/used elastic ips and provides ui warnings when launching instances where there are none are available • broadcaster system logs can now be downloaded via the broadcaster ‘details’ page the broadcaster details page now provides a link to download broadcaster system logs directly, without the user needing to navigate and log in to the broadcaster gui directly additional improvements and changes the following additional improvements and changes were implemented in this release • filtering in tables now evaluates on error/warning message contents o the event log message is now an option when using ‘add filters’ in the sources and channels tables • when selecting transcoding profiles, the list now displays codec • private ip streaming now works on clusters with dtls enabled • improved error handling in case users break zm aws iam role • added aws instance id to broadcaster details page • renamed vip tags to priority • disabled az rebalance process for aws clusters o this will only affect new or updated clusters • added pad to cbr options to demux sources • ignore pcr accuracy errors when monitoring vbr streams • multiplex sources now support auto pulls o requires broadcaster v16 7 • added options to customize the cloud init launch script on aws clusters • pid mapping changes are now tracked and displayed for all pid mapping modes • event log object names are now links to the specific objects • created features guide for new tables • automation task delay is now limited to 15 minutes • zm tags now propagate to azure • added billing codes to zixi push targets • applied new tables everywhere + other ui improvements bug fixes the following issues were resolved • fixed duplicate incidents • missing scte 35 alarm no longer stops working after an hour of missing scte messages • users unable to reset their own password • some fields always blank in grids • editing inter cluster source no longer creates an infinite loop • fixed diagrams showing broken active broadcaster in some cases • fixed unable to enable targets in some cases • removed alternative host from zixi push output in aws mediaconnect targets • automation tasks will no longer fail if execution takes longer than 3 minutes • fixed grids in grid groups missing an all good indicator when there is nothing to display in the grid • fixed pull connections to broadcasters/zecs not reconnecting on zero bitrate when a better source is available • requires broadcaster v16 7 • failover sources/channels will now work with auto pulls • added missing force delete options when deleting multiple tags • zm will now ignore certain irrelevant broadcaster errors when redirecting pull connections, e g full hard drive • update default adaptive fec settings on zixi pull sources