The default behavior is that whenever an object enters an error state all users who have access to that object receive email notifications about the Error. There are four methods for limiting the notifications that are sent out.
- You can Mute a specific object, stopping all notifications related to that object for all all users.
- You can Manage the notification settings for a specific type of error event adjust the Event Profile that applies to the object, see Configuring Events Profiles. This enables you to adjust each rule in the profile individually, specifying the following settings:
- Enabled/Disabled - Specify whether or not this rule is enabled for generating Events.
- Thresholds - For rules that are governed by thresholds (e.g.
Source offline, Source missing etc.)- CPU usage, low bitrate), specify the thresholds for generating warning and error events.
- Escalation - Specify the number of events that cause escalation from "warning" to "error" Events and the window of time that is considered for escalation.
- Notifications - Specify which Events trigger notifications.
- Flapping Detection automatically mutes an object on a temporary basis when it repeatedly goes into an error state. You can configure the settings for when this takes effect.
- You can adjust the thresholds for certain Error and Warning notifications that relate to excessive CPU/GPU usage. This is done within the configuration for each specific Broadcaster Cluster, see Adding a Broadcaster Cluster - Managed.
| Child pages (Children Display) |
|---|
