Managing Error Notifications

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 users you can adjust the event profile that applies to the object, see configuring events profiles docid\ cwshwpvmdch ryl86imts 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 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 temporarily 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 docid 6slx4td zkr2xfho8qz6 muting objects docid 60rcyl flgdg5tgwmiasl flapping detection docid\ sha6sanwt1okg z9vdxdd