Flow chart showing the decisions during custom alarm actions. The events occur in this order: testing begins. An FPU error is detected, and the error message logged in the error log file. Because the Fatal pattern is detected, a critical alarm is raised, recorded in the Alarms tab, and displayed in the Hierarchical View panel. The appropriate script runs and takes the processor offline. In addition, because the FPU pattern is detected, an Alert alarm is raised and recorded (but not displayed, because the critical alarm takes precedence) and an email is sent to the appropriate recipient. The custom alarm setup allows two actions to occur: the script and the email.