You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/event-alarm-framework/event-alarm-framework.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -71,9 +71,9 @@ It is not in the scope of the framework to update ANY of the applications to rai
71
71
72
72
# 1 Feature Overview
73
73
74
-
The Event and Alarm Framework feature provides a centralized framework for applications in SONiC to raise notifications and store them for NBIs to listen and fetch to monitor the device.
74
+
The Event and Alarm Framework feature provides a centralized framework for applications in SONiC to raise notifications and store them for north bound interfaces to listen and fetch to monitor the device.
75
75
76
-
Events and Alarms are means to indicate a change in the state of the system that operator may be interested in.
76
+
Events and Alarms are notifications to indicate a change in the state of the system that operator may be interested in.
77
77
Such a change has an important metric called *severity* to indicate how critical it is to the health of the system.
78
78
79
79
* Events
@@ -112,7 +112,7 @@ Both events and alarms get recorded in a new DB called EVENT DB in a new redis i
112
112
113
113
All events with an action field of *RAISE* get recorded in a table, by name, "ALARM" in addition to getting recorded in Event Table ( only events corresponding to an alarm has action field ).
114
114
When an application that raised the alarm clears it ( by sending an event with action *CLEAR* ), the alarm record is removed from ALARM table.
115
-
An user acknowledging a particular alarm will NOT remove that alarm record from this table; only when application clears it, the alarm is removed from ALARM table.
115
+
A user acknowledging a particular alarm will NOT remove that alarm record from this table; only when application clears it, the alarm is removed from ALARM table.
116
116
117
117
In effect, ALARM table contains outstanding alarms that need to be cleared by those applications who raised them.
118
118
This table is NOT persisted and its contents are cleared with a reload.
@@ -123,7 +123,7 @@ In addition to the above tables, the framework maintains various statisitcs.
123
123
124
124
1. Event Statistics Table
125
125
126
-
Statistics on number of events and alarms are maintained in EVENT_STATS table.
126
+
Statistics on number of events are maintained in EVENT_STATS table.
0 commit comments