Alarms

An alarm is an unexpected condition in EDA or the EDA-managed network that can be cleared by attaining some corrective state. The primary purpose of an alarm is to bring some abnormal condition to the attention of an operator, and thereby support debugging and resolution.
Note: An alarm is distinct from an event. An alarm represents a condition that should be corrected by reaching some associated corrective state. An event is a one-time occurrence and message (typically a log entry) about something that has occurred in the system. No future state is expected to clear an event, and it does not require an action to clear. Alarms are stateful; events are not.

Alarms in EDA can arise from a variety of sources, including the EDA system itself and the wide array of supported apps. For any alarm, the source/affected object is identified as part of the alarm in the resource, group, and kind fields.

Alarms are also associated with a namespace; this could be the base EDA namespace, or some other namespace. Users can only see and interact with alarms in namespaces for which they have access permissions.

Some alarms can be generated by intent-based apps within EDA. EDA treats such alarms as having been cleared if the app stops reporting that alarm.

Alarms associated with apps are described in documentation for individual apps.

Alarms on standby clusters

Standby cluster alarms can be important in understanding the state of redundancy in an EDA cluster. It is therefore useful to be able to see alarms generated on a standby cluster member even when working with the active member.

EDA supports this using the `cluster_member` field, which is set to the name of the cluster member that raised the alarm. This allows an operator to view alarms for all clusters, but still distinguish alarms for the active cluster from those for a standby cluster. For alarms that are not cluster-specific, this field remains unset.

Alarms in the EDA GUI

The EDA GUI includes several summary views of alarms known to EDA:

  • An alarm summary is displayed on the EDA home page.
  • A more detailed summary of alarms affecting key EDA components (clusters, Git servers, App catalogs and registries) is displayed on the main Alarms Summary page
  • The Alarms list displays a list of all active alarms
From the Alarm list, you can do the following for individual alarms, or as a bulk operation to a number of concurrently selected alarms:
  • Suppress an alarm: this sets the suppressed flag for the current instance of the alarm. By default, suppressed alarms are not displayed in the EDA GUI.
    Note: You can still view suppressed alarms by choosing "Show all alarms" from the Alarm List Table Settings and Actions menu.
  • Delete an alarm: this removes all history of the alarm. Deletion is only allowed for cleared alarms. The option is disabled for active alarms.
  • Acknowledge an alarm: this sets the Acknowledged flag for the current instance of the alarm.

Alarm definition resources

EDA core services and EDA applications document their supported alarms as alarm definition resources. These resources are available via the query .namespace.resources.cr.core_eda_nokia_com.v1.alarmdefinition. This query allows operators to retrieve a list of supported alarms that is specific to their deployed apps and versions.

The alarm definition specifications include the following fields:

Table 1. Alarm definition specifications
Specification Description
SourceGroup

Specifies the group of the resource that raises the alarm, for example, interfaces.eda.nokia.com.

Identifies the application that raises the alarm. EDA core alarms have the source group core.eda.nokia.com.
Type Specifies the alarm type, for example, InterfaceDown.
Description Specifies the description of the alarm.
ClusterSpecific

If this specification is true, the alarm is raised against a specific EDA cluster.

For example, a raised DeploymentDegraded alarm specifies which EDA cluster (active or standby) has a Kubernetes Deployment with one or more replicas that are not running.
Severity (optional)

Specifies alarm severity.

If not set, the alarm severity is variable. For example, the CPUThresholdExceeded alarm increases severity based on the CPU utilization value.
Kind and Group (optional)

Specifies the Kind and Group of the resource which the alarm is associated with.

For example, an InterfaceDown alarm is raised against an Interface resource. The Kind is Interface and the Group is interfaces.eda.nokia.com.
Note: An alarm definition is unique to the combination of SourceGroup and Type specifications. For example, both the Routing and Services apps can raise an alarm type BFDSessionDown. These are separate alarm definitions.

The Alarms Summary

Figure 1. The Alarms Summary page
Table 2. Elements of the Alarms Summary page
# Dashlet Description
1 Active Alarms count The Active Alarms count dashlet displays a total count of alarms affecting EDA applications and the EDA platform itself. This dashlet also displays the count of acknowledged and unacknowledged alarms.
2 Suppressed Alarms The Suppressed Alarms dashlet displays the count of suppressed alarms.
3 Active Alarms charts The Active Alarms charts dashlet breaks the Application Alarm and Platform Alarm counts down by severity and displays them in charts.
4 Active Application Alarms Building on the data displayed in the Active Alarms panel, the Active Application Alarms dashlet lists the active alarms affecting EDA applications, their severity, and their type.

Clicking the View link opens the Alarms List.
5 Active Platform Alarms The Active Platform Alarms dashlet lists the active alarms affecting the EDA application, their severity, and their type.

Clicking the View link opens the Alarms List.

The Alarms list

Figure 2. The Alarms list
Table 3. Elements of the Alarms list
# Name Function
1 Alarms menu The Alarms menu includes:
  • common table controls
  • multi-row actions unique to alarms
  • special actions unique to the alarms list
2 Alarm count Displays the number of current alarms of various severities.
3 Alarm quick filters Allows you to hide alarms using the following filters:
  • Cleared – filters out cleared alarms
  • Suppressed – filters out suppressed alarms
  • Child alarms – filters out child alarms

These filters are all selected by default.

Columns

The list of alarms displays the following columns by default.

Table 4. Default alarm display columns
Column Description
Namespace Indicates the namespace to which the alarm belongs.

Alarms that are not specific to a namespace, such as platform certificate alarms, do not have or display a namespace value.
Type The alarm type, as defined by the alarm itself. For example, InterfaceDown.
Severity The importance of the alarm, as defined by the alarm itself. Supported severities are:
  • Critical
  • Major
  • Minor
  • Warning

You can click this column to sort by severity level.
Resource Indicates the name of the resource that this alarm is present on.
  • For example, if an alarm was raised against a Fabric, the endpoint would be set to the name of the specific instance of a Fabric the alarm was raised against.
  • A resource may also be an instance of a resource in the Kubernetes cluster where EDA is deployed. For example, the resource may be the name of a Pod.
Kind Indicates the kind of resource the alarm is present on.
  • For example, this is set to Fabric if an alarm is raised against a Fabric resource.
  • The kind may also be a component with the EDA core - for example, ConfigEngine or StateEngine.
Group Indicates the group of the resource the alarm is present on.

For example, this is set to fabrics.eda.nokia.com if an alarm is raised against a Fabric.
Acknowledged Indicates whether the alarm has been acknowledged (True or False)
Occurrences The number of occurrences for the alarm.
Last Changed Indicates the time the alarm last changed state. The timestamp is updated any time an alarm changes state between cleared and not cleared.

The following alarms can be optionally displayed in the list of alarms by selecting Manage columns from the Alarms menu.

Table 5. Non-default alarm display columns
Column Description
Name Indicates the name of the alarm.
Description The description of the alarm from the alarm's encoded Description field.
Cleared Whether the alarm has been cleared by an operator. Possible values are:
  • True
  • False

This column is visible if the Active only filter is turned off.
Cluster Member For EDA platform alarms, the EDA cluster member to which the alarm applies.
Probable Cause The probable cause of the alarm, from the alarm's encoded Probable Cause field.
Remedial Action The suggested remedial action to resolve the alarm, from the alarm's encoded Remedial Action field.
Acknowledged Until If the alarm has been temporarily acknowledged, this indicates the date and time at which the acknowledgement expires.
Last Acknowledged Indicates the date and time when the most recent acknowledgement occurred for this alarm.
Last Acknowledged By Indicates the user who last acknowledged the alarm.
Suppressed Until If the alarm has been temporarily suppressed, this indicates the date and time at which the suppression expires. This column is visible if the Hide suppressed filter is turned off.
Suppressed Indicates whether the alarm has been suppressed. This column is visible if the Hide suppressed filter is turned off.
Last Suppressed Indicates the date and time when the most recent suppression occurred for this alarm.
Last Suppressed By Indicates the user who last suppressed the alarm.
Source Resource The EDA-managed resource from which the alarm originates.
Source Kind The kind of resource from which the alarm originates.
Source Group The group of the resource from which the alarm originates.
JS Paths The EDB entry which triggered the raising or clearing of the alarm, in JSPath notation. For example, if the alarm pertains to an interface operational state, this may be the JSPath: .node{.name=="spine-1"}.srl.interface{.name=="ethernet-1/14"}
Parent Alarms Indicates whether the alarm is associated with one or more parent alarms. It is common for alarms to have one or more parents. For example, an InterfaceDegraded alarm may be caused by one or more of its component members being down; that condition is itself the subject of a separate alarm. This column is visible if the Root cause only filter is turned off.
Targets Affected Indicates the number of child items which show the correlation between an alarm and the target it affects.

The Alarms Information panel

The Alarms list page contains an Information panel that you can open by clicking the Expand/Contract control at the middle right of the page. This Information panel appears throughout the EDA GUI, for details see Information panel. The following figure shows an example of an expanded Alarms Information panel for a selected alarm.

Figure 3. The expanded Alarms Information panel
The Information panel displays information about any selected alarm in the Alarms list. This information includes the following grouped and collapsible fields:
  • Alarm Summary – includes Name, Namespace, Type, Severity, Cleared, Resource, Description, Kind, Group, Occurrences, Acknowledged, and Last Changed fields
  • Remediation – includes Parent Alarms, Probable Cause, and Remedial Action fields
  • Additional Properties – includes Acknowledged Until, Last Acknowledged, Suppressed, Suppressed Until, Last Suppressed, Source Resource, Source Kind, Source Group, and JS Path fields

Fields that are empty or not applicable are hidden.

The following table describes the navigation from the Information panel to Parent Alarms and Resource locations.
Table 6. Information panel navigation details
Location Description
Alarm Summary > Resource

Displays the resource information for the selected alarm.

Click Go to resource to view the details of the alarm resource.
Remediation > Parent Alarms

Displays the parent alarm of the selected alarm.

Click Go to parent alarm to display the Details page for the parent alarm of the selected alarm.
Additional Properties > JS Paths

Displays the JS path for the selected alarm.

Click Go to Query Builder to display the Query Builder page for the selected alarm.

Sample core alarms

Table 7. Repository Reachability Down
Property Description
Name RepositoryReachabilityDown-<cluster>-<server-name>-<repo-type>-<source>
Severity Critical
Description Connectivity between <source-kind> "<source>" and the "<repo-type>" repository at "<server-uri/remote-path>" is down. This alarm is raised after three failures to connect to a repository, where each attempt is made at a 15s interval. After three failures the alarm is generated (so after 45s) and is cleared on a connection attempt succeeding.
Probable cause Connectivity issues, Kubernetes CNI misconfiguration, or credential/TLS misconfiguration/expiration.
Remedial action Restore connectivity between the corresponding <source-kind> and apps repository/Git server. Ensure credentials and proxy configuration are correct, and any offered certificates are trusted.
  • server-name is the name of the Git server hosting the repository, for example primary.
  • repo-type is the type of repository, one of Apps, Backup, Identity, Security, Catalog, UserSettings.
  • source is the name of the pod that raised the alarm, for example eda-se-1.
  • source-kind is one of ConfigEngine, StateEngine, AppStore.
  • cluster is the name of the cluster member that this alarm was raised in, populated via setting the clusterSpecific flag.
  • server-uri/remote-path is the combination of the server URI and remote path as defined in the EngineConfig.
Table 8. Service Reachability Down
Property Description
Name ServiceReachabilityDown-<cluster>-<service>-<source>
Severity Critical
Description Connectivity between <source-kind> "<source>" and the <kind> on "<service>" is down.
Probable cause Connectivity issues between worker nodes in the Kubernetes cluster, Kubernetes CNI misconfiguration, pod failure, or TLS misconfiguration/expiration.
Remedial action Restore connectivity between the corresponding source and destination. Ensure credentials and proxy configuration are correct (typically using no proxy for inter-cluster HTTPS), and certificate validity.
  • service is the common name of the destination pod, for example eda-npp-leaf-1-1.
  • source is the name of the source pod that raised the alarm, for example eda-sc-1.
  • source-kind is one of APIServer, ConfigEngine, StateEngine, AppStore.
  • cluster is the name of the cluster member that this alarm was raised in, populated via setting the clusterSpecific flag.
Table 9. Pod Not Running
Property Description
Name PodNotRunning-<cluster>-<pod>
Severity Critical
Description Pod "<pod>" is not in the "Running" state. Any functionality provided by this pod is not available. This alarm can be raised transiently at system startup.
Probable cause Kubernetes controller or registry reachability issues, worker node failure, initial instantiation.
Remedial action Validate reachability to the registry used to pull the image for the specified pod, ensure no worker node, storage, or networking issues exist that would cause the Kubernetes controller to mark the pod in any state other than "Running".
  • cluster is the name of the cluster member that this alarm was raised in, populated via setting the clusterSpecific flag.
  • pod is set to the name of the pod that is not running, but should be.
  • config-engine is set to the name of the ConfigEngine pod that raised the alarm.
Table 10. Deployment Degraded
Property Description
Name DeploymentDegraded-<cluster>-<deployment>
Severity Critical
Description Deployment "<deployment>" has at least one replica not in the "Running" state. Depending on the application this may result in loss of functionality or loss of service capacity. This alarm can be raised transiently at system startup.
Probable cause Kubernetes infrastructure issues, worker node failure, initial instantiation.
Remedial action Validate reachability to the registry used to pull images for any failed pods in the Deployment, ensure no worker node, storage, or networking issues exist that would cause the Kubernetes controller to mark pods in any state other than "Running".
  • cluster is the name of the cluster member that this alarm was raised in, populated via setting the clusterSpecific flag.
  • pod is set to the name of the pod that is not running, but should be.
  • config-engine is set to the name of the ConfigEngine pod that raised the alarm.
Table 11. Deployment Down
Property Description
Name DeploymentDown-<cluster>-<deployment>
Severity Critical
Description Deployment "<deployment>" is down, with no pods in the "Running" state. Any functionality provided by the Deployment is not available. This alarm can be raised transiently at system startup.
Probable cause Kubernetes infrastructure issues, worker node failure, initial instantiation.
Remedial action Validate reachability to the registry used to pull images for failed pods in the Deployment, ensure no worker node, storage, or networking issues exist that would cause the Kubernetes controller to mark pods in any state other than "Running".
  • cluster is the name of the cluster member that this alarm was raised in, populated via setting the clusterSpecific flag.
  • pod is set to the name of the pod that is not running, but should be.
  • config-engine is set to the name of the ConfigEngine pod that raised the alarm.
Table 12. NPP Down
Property Description
Name NPPDown-<cluster>-<npp>
Severity Critical
Description Connectivity between ConfigEngine "<config-engine>" and the NPP "<npp>" is down. This results in no new transactions succeeding to targets served by this NPP (unless operating in null mode), and no telemetry updates being received. Effectively targets served by this NPP are offline. Look for a corresponding PodNotRunning alarm.
Probable cause Connectivity issues between worker nodes in the Kubernetes cluster, Kubernetes CNI misconfiguration, pod failure, or TLS misconfiguration/expiration.
Remedial action Restore connectivity between the corresponding ConfigEngine and the destination NPP. Ensure credentials and proxy configuration is correct (typically using no proxy for inter-cluster HTTPS), and certificate validity.
  • cluster is the name of the cluster member that this alarm was raised in, populated via setting the clusterSpecific flag.
  • npp is set to the name of the destination NPP.
  • config-engine is set to the Pod name of the ConfigEngine that raised the alarm.
Table 13. Pool Threshold Exceeded
Property Description
Name PoolThresholdExceeded-<pool-type>-<pool-name>-<pool-instance>
Severity Varies; see definitions
Description The "<pool-instance>" instance of the <pool-type> "<pool-name>" has crossed the <severity> threshold of <threshold>.
Probable cause Pool utilization.
Remedial action Expand the pool via growing a segment or add additional segments. Additionally, you may move pool consumers to a different pool.
  • pool-type is the pool type, one of Subnet, IPInSubnet, Index, IP.
  • pool-name is the name of the allocation pool, for example ipv4-pool.
  • pool-instance is the name of the instance of the pool, for example global.
  • severity is the severity of the alarm, which increases based on which threshold has been breached.
  • threshold is the value of the threshold that has been breached, for example 80.
  • config-engine is the pod name of the ConfigEngine raising the alarm.
Table 14. State Engine Reachability Down
Property Description
Name StateEngineReachabilityDown-<state-engine>-<state-controller>
Severity Critical
Description Connectivity between State Controller "<state-controller>" and the State Engine "<state-engine>" is down. This results in no new state application instances being deployed to the corresponding State Engine, and the rebalancing of already-pinned instances to other State Engines. This connectivity is also used to distribute the map of shards to State Engine, meaning the corresponding State Engine is not receiving shard updates (assuming it is still running).
Probable cause Connectivity issues between worker nodes in the Kubernetes cluster, Kubernetes CNI misconfiguration, pod failure, or TLS misconfiguration/expiration.
Remedial action Restore connectivity between the corresponding State Controller and the destination State Engine. Ensure credentials and proxy configuration are correct (typically using no proxy for inter-cluster HTTPS), and certificate validity.
  • state-engine is the name of the State Engine with connectivity issues, for example eda-se-1.
  • state-controller is the name of the State Controller pod that raised the alarm, for example eda-sc-1.

Viewing alarms

Follow this procedure to view the set of alarms known to EDA.
Note: By default, the alarm list:
  • is sorted first by "Severity", and then by the "last changed" timestamp in descending order (most recent change first)
  • hides any suppressed alarms
  1. In the EDA main menu, select Alarms to open the Alarms page.
  2. To include suppressed alarms (which are hidden by default), do the following:
    1. Click the More icon at the upper right of the Alarms page.
    2. Select Show All Alarms from the displayed list.
  3. To exclude suppressed alarms from the list, do the following:
    1. Click the More icon at the upper right of the Alarms page.
    2. Select Hide suppressed alarms from the displayed list.

Acknowledging an alarm

When you acknowledge an alarm, you can:
  • Acknowledge the alarm permanently.
  • Acknowledge the alarm temporarily, after which the alarm returns to its unacknowledged state.
When you acknowledge an alarm temporarily, you can choose from a list of predefined periods, or select a specific time and date for the acknowledgement to expire.
Figure 4. Temporarily acknowledging an alarm
  1. In the EDA main menu, select Alarms to open the Alarms page.
  2. Find the alarm in the list using the sorting and filtering controls.
  3. At the right side of the row, click the Table row actions button.
  4. Click Acknowledge from the list.
  5. Optionally, you can choose to acknowledge the alarm only temporarily by doing either of the following:
    • Click the drop-down control and click one of the standard periods displayed.
    • Click the drop-down control, then click Custom, and in the resulting window select a date and time for the acknowledgement to expire.
  6. Click Acknowledge to complete the acknowledgement of the alarm.

Acknowledge multiple alarms

When you acknowledge multiple alarms, you can:
  • Acknowledge the alarms permanently
  • Acknowledge the alarms temporarily, after which all of the selected alarms return to their unacknowledged state.
When you acknowledge alarms temporarily, you can choose from a list of predefined periods, or select a specific time and date for the acknowledgement to expire.
  1. In the EDA main menu, select Alarms to open the Alarms page.
  2. Use the sorting and filtering controls to display the necessary set of alarms in the list.
  3. Select all of the alarms you want to acknowledge by checking the box at the left edge of the list. Click the check box again to unselect any alarm.
    Note: To select all alarms in the list, check the check box in the title row. Click the check box again to unselect all alarms in the list.
    Note: The number of alarms you have selected, as well as the total number of alarms, is indicated at the lower right of the Alarms page.
  4. At the upper right of the Alarms page, click the Table settings & actions button.
  5. Select Acknowledge from the list.
  6. Optionally, you can choose to acknowledge the alarm only temporarily by doing either of the following:
    • Click the drop-down control and click one of the standard periods displayed.
    • Click the drop-down control, then click Custom, and in the resulting window select a date and time for the acknowledgement to expire.
  7. Click Acknowledge to complete the acknowledgement of the selected alarms.

Deleting a single alarm

An alarm cannot be deleted unless it has first been cleared.
  1. In the EDA main menu, select Alarms to open the Alarms page.
  2. Find the alarm in the list using the sorting and filtering controls.
  3. At the right side of the row, click the Table row actions button.
  4. Click Delete from the list.
    Note: The Delete option is not displayed for an alarm that has not been cleared.
  5. Click Confirm to complete the acknowledgement.

Deleting multiple alarms

An alarm cannot be deleted unless it has first been cleared.
  1. In the EDA main menu, select Alarms to open the Alarms page.
  2. Use the sorting and filtering controls to display the necessary set of alarms in the list.
  3. Select all of the alarms you want to delete by checking the box at the left edge of the list. Click the check box again to unselect any alarm.
    Note: To select all alarms in the list, check the check box in the title row. Click the check box again to unselect all alarms in the list.
    Note: The number of alarms you have selected, as well as the total number of alarms, is indicated at the lower right of the Alarms page.
  4. At the upper right of the Alarms page, click the Table settings & actions button.
  5. Click Delete in the list.
  6. Click Confirm to complete the acknowledgement for all alarms.
    Note: If some of the alarms you selected were not eligible for deletion, only those that were eligible are deleted by this operation. Ineligible alarms are not deleted. No error message displays in this case.

Suppressing a single alarm

When you suppress an alarm, you can:
  • Suppress the alarm permanently.
  • Suppress the alarm temporarily, after which the alarm returns to its unsuppressed state.
When you suppress an alarm temporarily, you can choose from a list of predefined periods, or select a specific time and date for the suppression to expire.
Figure 5. Temporarily acknowledging an alarm
  1. In the EDA main menu, select Alarms to open the Alarms page.
  2. Find the alarm in the list using the sorting and filtering controls.
  3. At the right side of the row, click the Table row actions button.
  4. Click Suppress from the list.
  5. Optionally, you can choose to suppress the alarm only temporarily by doing either of the following:
    • Click the drop-down control and click one of the standard periods displayed.
    • Click the drop-down control, then click Custom, and in the resulting window select a date and time for the suppression to expire.
  6. Click Confirm to complete the alarm suppression.
    Note: By default, suppressed alarms are not displayed in the alarms list. Unless you have selected to show all alarms, suppressing an alarm causes it to vanish from the alarms list.

Suppressing multiple alarms

Just as with single alarms, when you suppress multiple alarms, you can:
  • Suppress the alarms permanently
  • Suppress the alarms temporarily, after which all of the selected alarms return to their unsuppressed state.
When you suppress alarms temporarily, you can choose from a list of predefined periods, or select a specific time and date for the acknowledgement to expire.
  1. In the EDA main menu, select Alarms to open the Alarms page.
  2. Use the sorting and filtering controls to display the necessary set of alarms in the list.
  3. Select all of the alarms you want to delete by checking the box at the left edge of the list. Click the check box again to unselect any alarm.
    Note: To select all alarms in the list, check the check box in the title row. Click the check box again to unselect all alarms in the list.
    Note: The number of alarms you have selected, as well as the total number of alarms, is indicated at the lower right of the Alarms page.
  4. At the upper right of the Alarms page, click the Table settings & actions button.
  5. Select Suppress from the list.
  6. Optionally, you can choose to suppress the alarm only temporarily by doing either of the following:
    • Click the drop-down control and click one of the standard periods displayed.
    • Click the drop-down control, then click Custom, and in the resulting window select a date and time for the suppression to expire.
  7. Click Confirm to complete the suppression for all alarms.
    Note: By default, suppressed alarms are not displayed in the alarms list. Unless you have selected to show all alarms, suppressing alarms causes them to vanish from the alarms list.

Viewing alarm details

You can switch between the Alarm Details page and the Alarm History pages by selecting Details or History from the drop-down list at the upper right of the page.

The bread crumb path allows you to navigate from the Alarms Summary page to the Alarms Details or History page.

Figure 6. Bread crumb path and drop-down menu
  1. In the EDA main menu, select Alarms to open the Alarms page.
  2. Find the alarm in the list using the sorting and filtering controls.
  3. Double-click the alarm.
    EDA opens the Alarm Details page, which shows the Alarm Summary information including the following grouped fields:
    • Alarm Summary – includes Name, Namespace, Type, Severity, Cleared, Resource, Description, Kind, Group, Occurrences, Acknowledged, and Last Changed fields
    • Remediation – includes Parent Alarms, Probable Cause, and Remedial Action fields
    • Additional Properties – includes Acknowledged Until, Last Acknowledged, Suppressed, Suppressed Until, Last Suppressed, Source Resource, Source Kind, Source Group, and JS Path fields

    Fields that are empty or not applicable are hidden.

Viewing alarm history

You can switch between the Alarm History and the Alarm Details pages by selecting Details or History from the drop-down list at the upper right of the page.

The bread crumb path allows you to navigate from the Alarms Summary page to the Alarms Details or History page.

Figure 7. Bread crumb path and drop-down list
  1. In the EDA main menu, select Alarms to open the Alarms page.
  2. Find the alarm in the list using the sorting and filtering controls.
  3. At the right side of the row, click the Table row actions button.
  4. Click History from the list.
    EDA opens the Alarm History window, which shows all events pertaining to the selected alarm including the following details:
    • Cleared (true/false)
    • Last change date and time
    • Probable cause
    • Remedial action
    • Acknowledged (true/false)
    • History of users who acknowledged
    You can use the standard sorting and filtering controls to manage the list.