Analyze Alarm#
Workflows → AAAnalyze Alarms
This workflow is used for AIOps purposes, and provides a tool for the AI to diagnose interface alarms. The workflow takes as input the name of an alarm, and looks for the Interface that is linked to it. When found, the workflow looks for any TopoLink resources that include this Interface, and checks for any alarm on the other end of the TopoLink.
This is useful in cases where an interface is down because of a problem on the remote end. For example, the link between nodes A and B may be disabled due to excessive packet errors received by the interface on B, which may be caused by a faulty transceiver. In this scenario, A would not have an idea as to why the interface is operationally down. The workflow allows an AI to reason as to why this interface is down, if both ends of the link are managed by EDA.
Dependencies#
The AnalyzeAlarm workflow has no strict dependencies on any EDA resources. If an alarm with the provided alarmName does not exist, it completes gracefully.
Referenced resources#
No resources are referenced by the AnalyzeAlarm workflow.
Custom Resource Definition#
To browse the Custom Resource Definition go to crd.eda.dev.
AnalyzeAlarm
SPEC
AnalyzeAlarmSpec defines the desired state of AnalyzeAlarm
-
INSERT ADDITIONAL SPEC FIELDS - define desired state of cluster Important: Run "edabuilder generate" to regenerate code after modifying this file
STATUS
AnalyzeAlarmStatus defines the observed state of AnalyzeAlarm
-
INSERT ADDITIONAL STATUS FIELDS - define observed state of cluster Important: Run "edabuilder generate" to regenerate code after modifying this file