Skip to content

Commit

Permalink
Update event-alarm-framework.md
Browse files Browse the repository at this point in the history
  • Loading branch information
spenugondaa authored Jan 14, 2022
1 parent b7c4b95 commit 73a8f30
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion doc/event-alarm-framework/event-alarm-framework.md
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ In addition to the above tables, the framework maintains various statisitcs.
When the alarm is cleared or acknowledged, the corresponding severity counter will be reduced by 1.
This table categorizes "active" alarms per severity.

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

- 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.
( maps to log-alert )
Expand Down

0 comments on commit 73a8f30

Please sign in to comment.