Editing Events Profile Rules

the rules for events profiles can be modified the options available to edit within a rule depend on the individual rule to edit an events profile rule go to configuration > events profiles and select the events profile for which you would like to edit the rules details of the selected events profile are shown at the right side of the screen in the rules tab, click edit rules the rules for your chosen events profile are shown rules are grouped first by resource type (e g adaptive channel, broadcaster, source, etc ), then by error group (e g usage, configuration, etc ), and then by the error name (low bitrate, low audio level, etc ) rules that have already been modified are shown in the modified list in alphabetical order, and rules in the default list have default settings rules list scroll through the list and click on the desired rule alternatively, you can use the search box at the top of the page to search for the desired rule the rule tab expands, showing the settings for that rule (the options available to edit within a rule depend on the individual rule, see table below ) edit the settings as desired when you modify the settings, the rule is marked as "not saved" (indicated at the end of the rule's title) to save the changes, do one of the following click save at the top of the rule's tab the rule is moved to the modified list, and you remain on the edit rules screen click save at the top or bottom of the edit rules screen the rules you modified are moved to the modified list, and you are returned to the rules tab of the events profiles screen, where the rules appear in the list under modified to restore an events profile rule to its default settings go to configuration > events profiles and select the events profile for which you would like to edit the rules details of the selected events profile are shown at the right side of the screen in the rules tab, click edit rules the rules for your chosen events profile are shown rules that have been modified are shown in the modified list in alphabetical order, and rules in the default list have default settings scroll through the list and click on the desired rule the rule tab expands, showing the settings for the r click the reset button at the top of the rule's tab the rule is reset to its default settings, automatically saved and moved back to the default list when you click on the "reset" button, the rule's settings are instantly reverted to their default settings and saved you cannot undo this action the table below lists all of the potential parameters from all of the rules there is also the option to reset rules to their default settings parameter description track only, do not update object state select this option if you want the escalation event to be registered in the event log only in this case, the issue triggering the rule and any resulting escalation, will not escalate the object itself to a warning or error state disable select this option to disable the rule entirely, so that no events will be logged for this rule (if checked, the other rule options are no longer shown ) generate ok email notification select this checkbox if you would like email notifications to be sent to relevant stakeholders when the object returns to an ok state generate error email notification select this checkbox if you would like notifications to be sent to relevant stakeholders when the object enters an error state ignore object state for notification generation select this checkbox if you would like notifications to be sent to relevant stakeholders for all error events regardless of whether the object was already in an error state (when not selected, notifications are only sent when an object first enters into an error state ) thresholds for value thresholds enter the threshold or adjust the slider to specify the thresholds for escalating/de escalating to/from a "warning" and "error" state in this case the value is absolute and defined within the rule (e g utilization level in percentage, time in days, etc ) for example, a cpu usage rule can determine that if the cpu utilization reaches above the 50% threshold, it will escalate to a "warning" state and if the value is above the 80% threshold, it will escalate to an "error" state if you want to disable the "warning" and/or "error" states de select their respective checkbox for state over time thresholds in the "warning" and "error" fields enter (or adjust the scale) the percentage of time in which the object should spend in the relevant state (e g in a "warning", "error" or "ok" state) within the time windows, which are specified in the warning/error window (minutes) in order to escalate the object to that state for example, 50% out of 6 minutes is an error threshold, so if a source reports a blank picture for 3 minutes out of the 6 min window, zm will put it into an error state however, if the warning threshold is 5% out of 60 minutes, if a source reports a blank picture for 3 minutes out of the 60 min window, zm will put it into a warning state if you want to disable the "warning" and/or "error" states de select their respective checkbox escalation/de escalation timing to protect against "flapping", the rule also includes de escalation and escalation delays that require the object to spend the configured time (in minutes) in the higher/lower state to actually escalate/de escalate the state warning de escalation delay specify the time in minutes in which the object should spend to de escalate from "warning "to "ok" state warning escalation delay specify the time in minutes in which the object should spend to de escalate from "warning "to "error" state error de escalation delay specify the time in minutes in which the object should spend to de escalate from "error "to "warning" state error escalation delay specify the time in minutes in which the object should spend to de escalate from "warning" to "error" state