Comment 4 for bug 1848580

Manage Alarm Debounce Algorithm
-------------------------------
General: Alarm state change at DEBOUNCE_THRESHOLD count.
         Effectively 3 mins of persistent severity assertion.

Debounce Conditions:

1. Need >= severity notification for DEBOUNCE_THRESHOLD
   consecutive counts to qualify for an alarm assertion.
2. One ok notification prior to alarm assertion will clear
   all accumulating severity level debounce counts.

Debounce Actions:

Clear: Once alarm is asserted (condition 2 above met) ...
       Every ok reading subtracts 1 from each severity level
       Every severity reading adds 1 to that severity count
       up to a max of DEBOUNCE_THRESHOLD.

Major: Add 1 to major debounce for every severity above
       ok reading until until count reaches
       DEBOUNCE_THRESHOLD and then raise major alarm.
       Any ok reading before alarm assertion clears counts

Critl: Add 1 to critical debounce for every critical
       severity notification reading until count reaches
       DEBOUNCE_THRESHOLD and then raise critical alarm.
       Any ok reading before alarm assertion clears counts