ZEN MASTER NOVEMBER 2018 RELEASE NOTES

the following updates were pushed to zen master on november 5, 2018 notification and error escalation configurability email notifications in zen master result from a sequence of events and, with this update, the user will now have more control over how objects transition to an error state and when notifications are sent previously, when a tr 101 or content quality event occurred on an object, such as a source, that object would transition to a warning state if the same event continued to happen on the same object for a two minute period of time, the object would transition to an error state upon transition to the error state, an email notification would be sent to users based on roles and groups note that more critical events, such as a source going offline, immediate transition to an error state and notifications are sent warning to error escalation now the user can set the escalation time window and set an escalation occurrence threshold warnings will escalate to an error if the object remains in a warning state for longer than the escalation window or if the number of warnings within the escalation window is greater than the occurrence threshold to edit the escalation window and occurrence threshold for a particular type of event, select an existing warning from an object event log and click manage next, choose if you want to update the escalation for this type of event only on the current object, or all objects of this type, and set the escalation time window and occurrences threshold you can also choose to disable escalations of this type of event from warning to error if you still want the object to escalate to an error in the log files, but not change state to warning, which is shown as orange indicators in the ui, select “hide warning state” if you want this event to not be saved to the log and to not escalate to warning or error state and to not create notifications, select “disable logging, do not change state and do not notify” once an event has been escalated to error state, the event needs to not occur again for the length of the escalation time window for the object to fall back to ok state if the event happens again during the time window, the clock resets on the time window and the object remains in error state for example, if the escalation window is set for 15 minutes, the object will only return to ok state if the event does not happen for 15 minutes if the event happens 5 minutes into the 15 minute window, then a new 15 minute window begins where the event must not happen for the object to return to ok state existing warning to error escalations can be managed under settings >notifications note an admin is able to overwrite a user’s escalation configuration, but the user can then recreate new escalation configurations notifications when an object transitions to error state, a notification is sent previously, all notifications for an object could be muted and this capability has not changed; it can be useful for misbehaving objects now, error notifications for each type of event, such as “incorrect continuity count”, can be enabled/disabled on a per user, per group, or per account basis to disable an event notification, click on manage in the events list for an object in error state next, if you are an admin user you can enable or disable the notification as account default or group default or only for your user id individual users can override this default just for their user id if you are not an admin user, you cannot set the account default or group default and can only enable or disable a notification for your user id next, you choose to disable the notification for only the current object or another object of the same type that you select from the pulldown or for all objects of the same type as the current object flapping detection configurability flapping detection will automatically mute notifications on an object that repeatedly changes state as long as the state changes continue to occur the object will remain muted the user can now set the size of the time window, number of state changes, and cooldown period; previously it was hardcoded flapping detection parameters are set under settings >notifications updated links for feeders and receivers the configure link for opening the feeder and receiver ui remotely is now the open link updated links for broadcasters the configure link for opening the broadcaster ui remotely is now the open link the cpu and memory history graph for the broadcaster can now be found by clicking the details link dtls broadcasters being managed by zen master will now use dtls to encrypt streams the broadcaster version must be v12 2 or later zen master will automatically create certificates for dtls so there is no need to manually create and upload certificates dtls is enabled/disabled on each broadcaster cluster on the cluster configuration dialog feeders and receivers connected to the broadcaster can be v1 11 or v12 when using v1 11 feeders and receivers, select ignore dtls certificate on the cluster configuration dialog normally, new broadcasters in a cluster with dtls enabled will have dtls configured automatically if dtls is not successfully configured, click the details link on the broadcaster and select configuration and click update configuration this will rewrite the configuration to the broadcaster and restart it and will show error messages than can help debug any issues user disable instead of needing to delete a user account and then recreate it, user accounts can now be disabled by an admin and then re enabled at a later time transcoding zen master will now show more detailed transcoding errors the transcoding profile dialog now allows the user to maintain the source aspect ratio transcoding enabled via zen master now supports the nvidia gpu and intel gpu, if the broadcaster reports that they are supported event filtering by access tag events can now be filtered by access tags events can now be filtered by access tags source thumbnail viewer thumbnails will now be displayed even when the source is in an error state the display of thumbnails is now more compact allowing more thumbnails per page error messages are now displayed as an overlay on the thumbnail instead of in whitespace between thumbnails finally, thumbnails wider than 16 9 aspect ratio are now displayed properly minor improvements and bug fixes • changed configure link to 'open' for clarity • fixed sql error in gui when attempting to delete account owner, now shows a pretty error • it is now impossible to create 2 users with the same email • fixed missing play button on sources with tr 101/cqa errors, play button will only be hidden if the source is offline • source selection in table when loading a new page, now paginates to the correct page instead of searching until there is only one page of data • fixed source history graphs reloading on their own • fixed 'duplicate entry' error on firefox browser • fixed push outputs reporting ok state when they are actually offline (caused by bad state reporting from the broadcaster)