---
title: ZEN MASTER May 2020 RELEASE NOTES
slug: zen-master-may-2020-release-notes
docTags: 
createdAt: 2025-03-20T16:09:59.118Z
---

The following updates were pushed to ZEN Master on May 18, 2020.


Kafka Integration



ZEN Master now exports events to Apache Kafka. Kafka is a data streaming platform that
allows you publish to and subscribe to streams of data, store them, and process them. ZEN
Master is a “publisher” that uses the Kafka Producer API to send event data to a Kafka server.
Once the event data from ZEN Master is streaming to a Kafka server, connectors are available
to pull data from the Kafka server into third party applications and services including
Elasticsearch, Splunk, Azure Event Hubs, AWS Cloudwatch, AWS S3, and more. The ZEN Master
Kafka integration has been validated with the Confluent Cloud service but should be compatible
with all Apache Kafka implementations.
To add a new Kafka integration, open the new ZEN Master UI:
Next, select Configuration->Notifications in the left-hand menu.

Select the Kafka Configuration tab and click Add.
Fill out the form using information from your Kafka service or server and enable the Events box.
Note, the Topic needs to have already been created on the Kafka server and Username / Password
authentication is required.
After configuring the Kafka integration, you can test it from the configuration tab where Kafka
integrations are listed.

Once configured, the Kafka integration operates with admin privileges meaning all events will be sent to
Kafka regardless of Access Tags. You can stop events being published to the Kafka topic by editing the
configuration and disabling the Events box. Also, if you disable logging for certain types of events on
certain objects (such as a Source), those events will no longer be written to the ZEN Master events
database or sent to Kafka servers.

### MINOR IMPROVEMENTS AND BUG FIXES


The following minor improvements were implemented:
• Updated Automation to support recently added Source and Target types including RIST, SRT,
UDP, and MediaConnect
• Pass-through channel Targets are now monitored for low bitrate and unrecovered packets
• Added ability to filter Broadcasters list by HostID and IP
• Added instance type to Broadcaster details page
• Added "Open" link to Channels diagram nodes to open remote Feeder/Receiver UI
• Updated PID analysis panel with new fields, including PTS, DTS, and Chroma, for consistency
with the Broadcaster UI
• Renamed Stream Quality/Delivery to Frame Delivery % and Packet Delivery %
• Updated missing fields for some Target types in public API
The following issues were resolved:
• Fixed issue where monitoring was ignoring Targets Broadcaster configuration causing invalid
Channel diagrams
• Fixed issue where pass-through Channel active Broadcaster logic was ignoring Source Target
Broadcaster configuration
• Fixed issue where the Receiver was not reconnecting on 0 bitrate source and required restarting
the Target
• Fixed issue where monitor only Sources could be played even when public output was disabled
• Fixed issue with Automation tasks stuck in executing state on overlapping schedules