To maximize the Servers pane, click this icon . To minimize the pane, click this icon .

Displays the user-defined name of the server on which one or more instances of the alarm exists. (This name is the name as specified in the Server Name field of the System Management Module that allows performing suite-wide system management activities from a single, Web-based application, the Enterprise Manager. > Enterprise > Settings screen for the server.

The server name displays as a link. To open the Enterprise Manager Agent Web application installed on every system server that communicates with the Enterprise Manager regarding any configuration changes or alarm messages for the relevant server. (EMA) or Recorder Manager (RM) application on the server, click the link. You can work with alarms in either of these applications.

Shows the Alarm Name as it appears in the user interface.

Note: Each alarm also has an internal alarm name, which is different from the Alarm Name that displays in the user interface. The internal alarm name is used by internal components of the alarm system and appears in log files.

Displays the number of instances of the alarm that have either the Active or Ack Pending status on a server.

These alarm statuses include:

• Active - Indicates the conditions causing the alarm still exist. To resolve the alarm, view the alarm details, perform the corrective action, and acknowledge the alarm.

• Ack Pending (date/time) - Indicates that the system is completing the alarm acknowledgment process, and shows the date and time when the alarm was acknowledged. This status displays immediately after an administrator, or the system, acknowledges an alarm.

  Note: The Ack Pending status usually exists for approximately 30 seconds after alarm acknowledgment. The status can exist longer when there is much alarm activity Core component of both schedules and time records in Workforce Management (WFM). When an employee performs any kind of work, activities specify the scheduled work and capture employee adherence to their schedule. on a server (or in other isolated cases In Risk Management, use cases to group interactionss according to the needs of the enterprise. Interactions can reside in multiple cases simultaneously.).

Lists the date and time at which the most recent alarm instance was raised (or triggered) on the server.

The time displays in the local time Time axis in the system that refers to the time on the clock in the location where the operation occurred. zone of the user viewing the Alarms Dashboard.

To acknowledge all instances of a specific alarm on the server, click the icon. Acknowledge an alarm only after you have performed the corrective actions required to fix all the conditions causing the alarm.