ZEN MASTER March 2023 RELEASE NOTES

the following updates will be included in the zen master march 02, 2023 release features the following new features were implemented in this release • re designed "state" based alerts management and escalation mechanisms the zen master alert escalation mechanism has been updated to provide better controls for determining when, or when not, underlying issues require escalation to the user via either a warning state, or a full error alert previously, zen master used the number of contiguous events in a polling cycle window, to escalate from good to warning, and from warning to error, before deescalating at the end of a clean window in the updated model the following enhancements and clarifications are introduced \ for state based alerts, zen master now uses the % of a given time window that an object spends in a non positive state, to determine if it should escalate \ warnings and errors use independent escalation and de escalation windows, allowing users to better refine the escalation o e g , a source reporting blank picture for 5% of 60 minutes as a whole might constitute a warning only, to be looked at later but a source reporting blank picture for 10% of a 15 minute window, can be configured to escalate to an error \ 2 distinct mechanisms now control the behavior of each alert, thresholds and delays thresholds thresholds determine the severity of the alert there are 2 types of thresholds, value thresholds, and state over time thresholds value thresholds e g , cpu/gpu/license expiration, these are simple, they have a warning value and an error value and the severity is determined by the measured value compared to the configured thresholds state over time thresholds for alerts that are based on a boolean state, whether it is boolean (e g , source offline) or because the exact value is not important (e g , cc errors or not recovered packets) the threshold is defined by a time window and a percentage of time of that window spent in the relevant state \ e g , 50% out of 6 minutes is an error threshold, so if a source reports a blank picture for 3 minutes out of the 6 min window, zm will put it into an error state \ to prevent edge cases where warning is always ignored, the system validates against the following configuration limits o warning threshold must be lower than error threshold o warning window must be greater or equal to error window delays in addition to the threshold zen master also now provides an escalation delay and a de escalation delay for each threshold a b de escalation – primarily used to protect against flapping, to de escalate to a lower state the object must spend a de escalation delay worth of minutes in a lower state than the current one escalation – similar to the de escalation window, the object needs to spend the configured number of minutes in a higher alert state before zen master will register it as an error usually left at zero, but in some cases, users may require an escalated state persist for a sustained period before being alerted i for example, users may not be concerned with short cpu spikes, but want to be alerted to sustained high cpu usage note that all defaults and any existing edited rules in customer event alert profiles have been converted to a best case match to approximate the old setting using the new mechanism • alert rule details and edit panel as with previous releases, any objects log of events contains an actions column for warnings and errors escalated by the alert event profile, that thus far contained 2 actions 1\ create an incident 2\ take the user directly to the full rule page for the alert event profile that was used to escalate the event to the log and elevated status as of this release, the action that previously took the user to the full event profile list, is now replaced with an action to bring up a panel related to the specific rule that triggered the alert the panel \ still provides access to the full event profile, but also \ provides in band controls to edit the specific rule in place and propagate to all objects using the profile \ provides the option to clone the full profile and assign the new profile, along with any changes, to this object alone 1\ to continue to and, if needed, edit the original profile, click the events profile name to jump to the full original event profile page 2\ here, edits to the rule, and how it deals with issue s and escalated then to errors and warnings can be made 3\ in the update portion of the dialog a select ‘overwrite’ to make changes and propagate to all objects sharing the existing profile b select ‘create new’ to make a clone the existing profile, that is otherwise identical except for the changes to this rule this will prompt the user for a required name for the new event profile • networks page showing the current networks in use by the customer and the objects on them the network tracking page is now available via a new top level left hand menu the page is self populated by auto discovery it provides details and object states about each network clicking on a network again provides the details tab, and a tab showing the specific objects that are active on the network • ability to share an abbreviated source page with a non zm user provides the ability to share a source object thumbnail page via a public link/url with external users, without requiring them to have a zen master account this can be used to share visibility into a source with user such as live event producers, service customers, external department, 3rd parties, and others with a need to view a source as a live looking in or during a live event the zen master operator can select or view a source and bring up the sharing controls the share controls provide start and end time controls to limit the longevity of the shared url, which is generated by choosing “create link” note in version 1, there is no link management or additional features the link will expire when the end time is reached at this release, links are limited to 24 hours user with access to the link will be able to view the temporary source details external user landing page, which visibility to \ name \ status \ thumbnail \ bitrate \ uptime \ optional overlay • aws wavelength zone support zen master now supports 5g contribution and distribution using the aws wavelength zone service, by \ providing the ability to launch an instance within the wavelength zone \ supporting the new instance types \ applying the appropriate carrier ip this can be achieved once the following pre requisites have been met before launching a wavelength zone instance, opt into the wavelength zone service by enabling the feature via your aws console once the service is available, the appropriate networking must be provided \ a vpc in your region \ a carrier gateway \ a subnet in a wavelength zone once complete, zen master enables the user to launch an instance in the wavelength zone subnet with a carrier ip address applied note that due to instant type and public ip differences, wavelength zone and non wavelength zone subnets are not interchangeable, and clusters can only choose one please see the aws documentation for more information on configuring your aws wavelength zone network what is aws wavelength? https //docs aws amazon com/wavelength/latest/developerguide/what is wavelength html get started with aws wavelength https //docs aws amazon com/wavelength/latest/developerguide/get started wavelength html available wavelength zones https //docs aws amazon com/wavelength/latest/developerguide/available wavelength zones html • external authorization support for zixi push sources and zixi pull targets to date, target pull requests reaching the i/o server are handled exclusively by zen master application, validating the request against the target configuration to authorize the connection just as the zixi broadcaster can redirect the authorization of connections to an external server, zen master now supports a similar functionality when configured, in addition to the standard internal authorization process, the requests redirected to an external service for confirmation an example of this could be an external pay per view application, which confirms that a requesting end device belongs to an account that has paid for a live event another example could be some external security management application that is managing firewalls accepting requests from dynamic ips in a consumer network configure external authorization in a clusters’ advanced settings \ configuration requires an external authorization url for the server endpoint \ optional authorization header schema and credentials • re architected aws medialive integration to allow sharing a single aws mediaconnect flow previously, a separate aws mediaconnect flow was required for each medialive workflow with this update, a single mediaconnect flow can be created, which is then able to act as the source of many medialive engines existing mediaconnect to medialive channels will convert seamlessly to the new architecture, allowing additional medialive outputs from historically active flows • upd/rtp target support for aws medialive channels the new option can now be found in the create new udp/rtp target dialog • improved filtering for tables along with the updated tables component zen master now introduces more refined filtering capabilities while the simple search bar still matches a search against all columns of the tables, the new filter provides additive column specific filter options that are specific to the column types of the correspond table this allows the user to set more fine grained filter parameters such as searching for text in specific columns, filtering with relational operators on numerical columns, or specifying time ranges etc filters are additive, so a sources search with a filter for uptime > 2 days, and a second for uptime < 3 days, will yield a result of all sources with uptimes between 2 and 3 days in this release the new filters appear on all major list pages, zecs, broadcasters, sources, channels, and targets, and persist if set before the user navigates away from the page and then returns additional improvements and changes the following additional improvements and changes were implemented in this release • updated look and feel • ui polish • all high level tables, including those on list pages and others, are updated to the new code • agentz now support arm hardware • live events list and detail pages now represent the live state of each live event with no delay • added channel name, ip, and bitrate support to targets in grids • added an option to control aws "detailed monitoring” of cloudwatch for aws clusters, providing users with ability to better control costs o on all existing clusters this is turned on o for new cluster, the option will default to off • reorganized data presentation of source details page, grouping categories for clarity • added support for ndi audio channel mapping • added option to create an aws mediaconnect source from a zec • updated channel list table to show source or target name instead of a count when a channel has only 1 of either • zen master will now correctly update existing and create any newly required auto pull configurations for a channel, whenever a source’s target broadcaster is edited o this saves the user from a manual disable/enable cycle on affected channels and targets • aws medialink is now its own source type in the ui o as with the aws medialink encoder directly supported outputs, zen master medialink source destinations are limited to an aws medialive channel only • updated the list of supported and available instance type options for aws clusters o some unused instance type options were removed o support is added for c7g and c6in families • improved the zen master logic for pull target redirection when considering scenarios such as offline sources o e g , offline source error are now considered lower priority than cqa/tr 101 • updated and clarified the event log message for broadcaster maintenance mode • ‘broadcaster restarted’ alert, which was previously captured by the broadcaster status error alert rule, now has its own standalone rule for finer control • thumbnails in source list are now off by default o this will not affect any browser that you already used to navigate to a sources list on, so they will remain for customers that did not turn them off already bug fixes the following issues were resolved • fixed multiple issues with new tables selection and updates when an object is deleted • fixed broadcaster terminated alert not obeying alerting profile rules • fixed bonding on aws mediaconnect sources • live events list page stage filter now persists after navigation • source links on live event dashboard now correctly take user to the source details page • user group details page now displays the actual role details • api target get with an invalid id now returns http code 404 instead of 500 • resolved multiple issues with export to excel quick reports in new tables • maintenance mode warning display now correctly obeys users read permissions on a cluster • removed irrelevant "requires restart" warning when editing a cluster • resolved dst issues with automation • editing a live event no longer resets its channel selection • enabling a source automation will no longer restart already enabled sources o remains true when enabled via the ui or the zen master api • zm will now log scte 35 messages with invalid crc • resolved and issue preventing function with azure transcoding broadcasters