# Manage alarms and events

## Alarm icons and alarm state descriptions

Alarm icons use a color code to indicate levels of severity. Alarms may trigger different automatic system responses, like failover. Certain intended, manual actions may trigger a notification event, like when you manually start or stop a service.

Color codes for alarm and event states:

- Alarms
  - `Alarm red` critical
  - `Alarm yellow` major
  - `Alarm green` minor
  - `Alarm` information

- States
  | State   | Description                                                                                                                                                                                                |
  | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  | raised  | An alarm is active and triggered. Service may be stopped or the server is down. A backup server may be used if [assigned in a failover group](/beam/system-admin/servers/failover#display-failover-groups) |
  | cleared | The issue related to the alarm is resolved. This includes restoring services after a failover to a backup server, even if the primary server is down.                                                      |

## Customize alarm display time

The alarm display refreshes automatically every few seconds.
By default, all timestamps are shown in Universal Time (UTC), but you can customize the time zone.

1. Click `Gear` in the upper right corner.
2. Select **Settings**.
3. In the **General** tab, choose your preferred **Alarm display time zone** from the drop-down list.
4. Click **Save** to apply the changes.

## Types of alarms

Different pages are dedicated to specific alarm displays. For example, the **Alarms** page is a centralized alarm overview, the **Service alarms** page displays alarms for the specific service, and the **Failover alarms** page displays alarm and event overviews.

### Alarms page

The alarms page centralizes all alarms and events into a table. The Alarms page is a general alarms overview.

> **Info:** See the [Service alarms page](/beam/system-admin/maintenance/alarms-events#service-alarms-page) or the [Failover alarms page](/beam/system-admin/maintenance/alarms-events#failover-alarms-page) for specific alarm information.

#### Display all alarms and events

The **Alarms** page is an overview of all alarms and events.

To access the **Alarms** page you can:

- Click **Alarms** on the left-side menu to access all **Active alarms**, **Alarm history** and **Alarm overrides**.

  ![view active alarms menu](/_machine-assets/1a948c678ed004fd445811420bc51759ba3a21ea75259fb3da2be4d36a8474d2.png)

- Click **Services** on the left-side menu then click `Alarm` in the **Alarm** column to display alarms for a specific service. The Alarm icon is the color of the active alarm with the highest level of severity.

- Use the shortcuts in the top-right corner banner.

  ![view alarm shortcut header](/_machine-assets/aedf4a92f3a3094e17048a921a5442d0eae384f00f5cdafe14284e0bcd4cabf2.png)

You can then use the sort options in the table headers or the search bar to filter on specific alarms, services or servers.

#### Display alarm history

The alarm history for all alarms displays in a tab in the **Alarms** page.

> **Info:** By default, the alarm history is stored for approximately 7 days, or a maximum of 100,000 alarm events.

1. Click **Alarms** from the left-side menu.
2. Click **Alarm History** to view the history for all alarms.
3. Use the sort options in the table headers or the search bar to filter on specific alarms, services or servers.
4. The **Auto refresh** button can be used to control whether new alarms automatically appear in the table. This can be useful to disable on a busy system to stop the screen scrolling.
5. Click the **Download history** button to download a .csv file containing the alarm history.

### Service alarms page

You can access the alarms for a specific service from the **Services** page. An icon in the **Alarms** column indicates that there is at least one alarm for the service. Alarm icons use a color code. The color of the alarm icon in the Alarms column is based on the highest severity alarm known for that service.

An alarm status icon displays per service in relation to the alarm with the highest severity for that service. More than one alarm may exist for a single service.

#### Display service-specific alarms page

The service-specific alarms display in a dedicated page that also displays the alarm history for the service.

1. Display **Services**.
2. Click the alarm icon in the **Alarms** column. The service alarms display.

### Failover alarms page

If a failover group exists, then certain critical alarms may trigger a failover. You can check alarms for failover groups, and then drill down to alarms to investigate servers and related services.

In the [Failover group page](/beam/system-admin/servers/failover#display-failover-groups), the alarm with the highest severity (in relation to the servers in the failover group) displays in the **Alarm Status** column.

> **Info:** The alarm display is automatically refreshed every few seconds. All time stamps are in **Universal Time (UTC)**.

#### Display failover alarms page

The failover alarms page displays alarms and the alarm history for servers in a failover group.

1. Display the **Failover** page from the left-side menu panel.
2. Click the alarm icon in the **Alarm Status** column.

The alarms for the failover group display. You can use failover alarms to determine if a server in the failover group has an alarm, and then if there are service alarms for services running on that server.

## Alarm forwarding (SNMP)

SNMP alarm forwarding requires you to define a destination where alarms are sent.

### Display the list of SNMP destination configurations

1. Click `Gear` in the upper right corner of the window.
2. Select **Settings** then click the **SNMP notifications** tab. The SNMP destinations display. You can use the search options or column filters to browse the SNMP notification configurations.

   ![view snmp trap destination table list mfmms](/_machine-assets/eacdb048a41bf5358031c5b8bbc2513dd01948ec6ce225509bdbb24f8f3f13c8.png)

### Add a new SNMP destination

1. Click `Gear` in the upper right corner of the window then select **Settings**.
2. From the **SNMP notifications** tab, click **Add destination**. The SNMP destination parameters display.
3. Enter the [SNMP parameters](/beam/system-admin/maintenance/parameters#snmp-parameters-settings-menu) to configure the destination and the version.

> **Info:** The parameters that display to edit SNMP destinations depend on the SNMP version.

5. Save settings to return to the list of SNMP configurations.

### Edit SNMP destination configurations

1. Click `Gear` in the upper right corner of the window then select **Settings**.
2. From the **SNMP notifications** tab, click `Edit` to display SNMP destination parameters.
3. Edit the [SNMP parameters](/beam/system-admin/maintenance/parameters#snmp-parameters-settings-menu) and save.

> **Info:** The parameters that display to edit SNMP destinations depend on the SNMP version.

![view snmp v3 parameters](/_machine-assets/d8f48fc2c332b25de49641b6356399e9cb7400aa4c7b6d086a889688a95933c8.png)
_Example of SNMP v3 configuration_

### Activate/deactivate SNMP notifications

1. Click `Gear` in the upper right corner of the window then select **Settings**.
2. From the **SNMP notification** tab, you can activateSNMP notifications either:
   - tick the **Activate** checkbox from the table where SNMP configurations are listed.
   - or click `Edit` and tick the **Activate** checkbox at the top of the SNMP parameters.

### Delete an SNMP destination server

1. Click `Gear` in the upper right corner of the window then select **Settings**.
2. From the **SNMP notifications** tab, click `Delete` to delete the SNMP destination configuration. You are prompted to confirm and delete.

## Alarm overrides

> **Info:** The alarm overrides feature requires specific user rights.

You can manually override alarm severity levels. You can also view the alarms that trigger failover. You can filter the alarms using the search bar.

> **Info:** Changing the **Triggers failover** value impacts the possibility of a failover occurring.

### Override an alarm severity

You can change the alarm severity to either critical, major, minor, notice or ignore. The initial default severity displays in the **Alarm overrides** tab if you need to revert to the initial default severity setting. Setting an alarm to "ignore" will exclude that alarm type from displaying in the active and historical alarm views. It will also be excluded from the API responses and SNMP traps. The only evidence of "ignored" alarms will be in log files.

> **Warning:** Changes to severity are only applied to future occurrences. Any current or previously existing alarms are unchanged.

1. Click **Alarms** in the left-hand menu panel.

2. Click the **Alarm overrides** tab to display options. The following page displays.

   ![view alarm overides controller](/_machine-assets/aaa90b80163c526039bdb41037f27cd70437a88ec17004329c4c021ef9301e30.png)

3. Click the **Current severity** for the specific alarm to display options. A list of severity options displays.

   ![view current severity button alarm override controller](/_machine-assets/7fd008701bfc4863e93ee01844e46c7c7502e0e34520f0a662a45be5cf3018bd.png)

4. Select a severity from the list. The **Current severity** changes.

> **Info:** Changing the severity may increase or decrease the possibility of failover occurrence.

![view alarm override select severity controller](/_machine-assets/0595ae2fad72a7878c7bd49bcbc93144ea841a4d5a97aaad072ddfb60b7bb6b2.png)

### Reset the alarm severity to the default setting

Alarm severity can be manually changed. You can reset the alarm severity to the default setting. Changing the **Triggers failover** value impacts the possibility of a failover occurring.

> **Warning:** Changes to severity are only applied to future occurrences. Any current or previously existing alarms are unchanged.

1. Click **Alarms** in the left hand menu.
2. Click the **Alarm overrides** tab to display options.
3. Click the **Default severity** for the specific alarm to display options. A list of severity options displays.
4. Select a severity from the list. The **Default severity** changes.

> **Info:** Changing the severity may increase or decrease the possibility of failover occurrence.

## Events

Events are displayed in the **Alarms** page. Events notify you of actions that do not impede proper functioning.

Example of an event when you intentionally start or stop a service:

![view active alarms menu table](/_machine-assets/2c153cf0ce76d741d86015c8b99fb57410dbb76d01e5f9c91bc3adb44beef8cd.png)