How do I setup EventAction to avoid receiving repeated alarms?
Sun Management Center triggers an event everytime a rule is satisfied. For example, if a monitored process consumes 90% of the cpu this triggers an alert alarm. When the process cpu falls below 90%, the event is closed and a new one is issued everytime the process cpu is greater than 90%. This sort of behaviour triggers an action more often than one is needed. EventAction allows you to set a deadband or a delayed alarm before an action is taken. In our example above, an action would only be taken if the event is still open after some specified time. The same feature can be used to escalate alarms that are not fixed by a specified period of time allowing notification to go from the user to management level.
Related Questions
- What if, after repeated attempts, I am unable to setup an appointment to meet with my Academic Advisor during any of his/her available times?
- I’ve heard that setup for RF superimposed DC is complicated. What are the main pitfalls to avoid?
- How do I setup EventAction to avoid receiving repeated alarms?
