Page in/out rules firing even though the rates are low (4308301)

Page in/out rules fire even though the rates are low.

Sample
Fatal: Abnormal page in rate 0.25.

The rules are triggering as they reach the threshold from the Intelliprofile baselining

The fireAfterNSuccesses function is designed to smooth out the rule's alarm-firing behaviour. It will only fire an alarm if the Page Out Rate exceeds the "INF_MemoryPageOutRateFatal" value (256.0) for a count of "INF_MemoryPageOutRateFatalCount" (1).
Basically, the Fatal alarm will only fire if the Page Out Rate exceeds 256.0 twice consecutively.

The rule also fire on a low values of 0.39 or other values which is related to how IntelliProfile defines the thresholds. 

The page in/out rate rule contains the Thresholds condition. These thresholds data depend on history data.

WORKAROUND:

Rule Name: Page Out Rate / Page In Rate
Description: This rule determines if host memory is demonstrating an abnormal page out rate.
Fatal Variables:

INF_MemoryPageOutRateLowestValue: 0.1
INF_MemoryPageOutRateFatal: 256.0
INF_MemoryPageOutRateFatalCount: 1

Note: you can find the same variables for PageIn.

If the baseline still triggers too many alarms, modify the following rules thresholds

1. Go to: Navigation Panel | Dashboards Section | Administration | Rules & Notifications | Rules Management
2. Select the following rules: "Page Out Rate", "Page In Rate" and disable them.
3. Copy and edit the copied rule(s).
4. This is one example (this can be changed according to your needs) of alarm threshold change:
   
   INF_MemoryPageOutRateFatalCount from 1 to 2
   INF_MemoryPageOutRateLowestValue from .1 to 5.0
   
   And the corresponding PageInRate variables.