Skip to content

Commit 73a8f30

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

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ In addition to the above tables, the framework maintains various statisitcs.
132132
When the alarm is cleared or acknowledged, the corresponding severity counter will be reduced by 1.
133133
This table categorizes "active" alarms per severity.
134134

135-
As mentioned above, each event has an important characteristic: severity. SONiC uses following severities for events and alarms as defined in opeconfig alarm yang.
135+
As mentioned above, each event has an important characteristic: severity. SONiC uses following severities as defined in opeconfig alarm yang.
136136

137137
- CRITICAL : Requires immediate action. A critical event may trigger if one or more hardware components fail, or one or more hardware components exceed temperature thresholds.
138138
( maps to log-alert )

0 commit comments

Comments
 (0)