Skip to content

Commit abdb39c

Browse files
authored
Update event-alarm-framework.md
1 parent 73a8f30 commit abdb39c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/event-alarm-framework/event-alarm-framework.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -71,9 +71,9 @@ It is not in the scope of the framework to update ANY of the applications to rai
7171

7272
# 1 Feature Overview
7373

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.
7575

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.
7777
Such a change has an important metric called *severity* to indicate how critical it is to the health of the system.
7878

7979
* Events
@@ -112,7 +112,7 @@ Both events and alarms get recorded in a new DB called EVENT DB in a new redis i
112112

113113
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 ).
114114
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.
116116

117117
In effect, ALARM table contains outstanding alarms that need to be cleared by those applications who raised them.
118118
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.
123123

124124
1. Event Statistics Table
125125

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.
127127

128128
2. Alarm Statistics Table
129129

0 commit comments

Comments
 (0)