Log Events
The following table describes the types of events that are logged for each type of system object and shows the severity level of each event.
All events are logged. In addition, Error events generate email notifications. You can customize the notification settings, see Notifications.
Object | Event | Level |
|---|---|---|
Feeder | Connection issues | Error |
API error | Warning | |
CPU/Mem above 90% | Error | |
Expired/missing license | Error | |
Broadcaster | Connection issues | Error |
API error | Warning | |
CPU/GPU/Mem/HDD above broadcaster configured limits | Error | |
GPU decoder/encoder usage above configured limits | Warning | |
Input/Output bandwidth above limits configured in Zen | Error | |
Expired/missing license | Error | |
Version not supported for various Zen features | Error | |
Configuration doesn't match Zen requirements (e.g. ports/dtls) | Error | |
|
| |
|
| |
Broadcaster Cluster
| Add |
|
|
| |
|
| |
|
| |
Receivers | Connection issues | Error |
API error | Warning | |
CPU above 90% | Error | |
Expired/missing license | Error | |
Source | Missing implementation (e.g. feeder output is not on the feeder) | Error |
Connection issues | Error | |
TR101 Priority 1 and CQA | Warning | |
Low bitrate, | Warning | |
Bitrate above max bitrate | Warning | |
Unrecovered packets | Warning | |
Content Analysis errors (if enabled in ZEN) | Error | |
Channel | Missing implementation | Error |
Missing inputs that are required for the channel | Error | |
Transcoding errors | Error | |
Target | Missing implementation | Error |
| Connection issues (e.g. GCP authorization errors, RTMP authorization errors etc.) | Error |
| HLS verification for adaptive targets (playlists are downloadable and chunks respond to http HEAD | Warning |
Remote Access | Checks if tunnel is alive | Error |
License | Checks if expired or expiring soon | Error |
Live Event |
|
|
Automation |
|
|
User Events |
|
|
Account Management | Logs updates and changes to security objects, including Users, Groups and Roles. |
|
