Global Visibility and Health

zen master's control plane collects and analyzes telemetry data across the entire stream workflow — from contribution through processing to delivery — giving operators the visibility they need to quickly identify and resolve issues analysis results surface in the incidents and insights modules, where users can visualize stream health at a glance sample source diagram visual diagrams of sources, channels, and targets make it easy to spot problems, and users can drill down into real time data on streams, devices, and networks for deeper diagnosis searchable event logs and customizable alerts keep operators informed and help them resolve issues fast graphs zen master provides a set of graphs in zen master that enable you to identify and diagnose areas of instability in your system brief descriptions are below; follow the links for more detailed explanations docid\ d75ifw fozxfd pptvxdw sample broadcaster graphs the docid\ d75ifw fozxfd pptvxdw graphs provide a visual history of various aspects of the broadcaster and the server or vm that it runs on these are useful for diagnosing problems that might be related to issues with broadcaster itself or the underlying system docid 7zape3l6cy 1z0vz9mxc source graph sample docid 7zape3l6cy 1z0vz9mxc graphs depend on the kind of source, whether you have enabled stream analysis, and so forth in all cases there will be a network graph showing the bitrate history docid\ gfii56tghka wmnr7n6y7 target history graph sample as with sources, zen master provides docid\ gfii56tghka wmnr7n6y7 graphs all targets will show a network graph that shows recovered and unrecovered missing packets, reconnections, and send errors for some target types, there is an additional bitrate history graph docid\ bgowcwcc5rmvqdkmlbttq and docid\ km0i5tnpzuo ygfv6qcvq events and incidents tables in the details for sources, channels, and targets provide a list of changes that occurred to help you identify and fix problems events (what happened , on a specific object) in zen master , an event is a single, atomic occurrence generated when an individual object changes state or violates a rule examples include a source going offline, bitrate dropping below threshold, audio clipping, or cpu utilization crossing a limit key characteristics events are generated per object (source, target, broadcaster, media connect flow, etc ) they are triggered by event rules defined in an event profile events represent state transitions (ok → warning/error, or back to ok) events are logged immediately and appear in the events view some events may trigger notifications (for example, email alerts) incidents (what broke , across multiple objects) an incident is a higher‑level construct that groups related events together in order to surface a likely common root cause according to the zen master user guide incidents group together related errors to simplify troubleshooting they can be automatically generated by the system or manually created by an operator automatic incidents are created when multiple objects (sources, targets, or broadcasters) experience error events around the same time and share a common resource the system uses correlation logic (time window, shared resource, and proportion of affected objects) to decide when to create an incident an incident has a date range , impact summary , and a root cause notice (for auto‑generated incidents)