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
Note: Both registry variable INF_MemoryPageInRateLowestValue and INF_MemoryPageOutRateLowestValue default value is 0.1.
By default the alarm can be fired when Page In/Out rate is larger than 0.1 and other condition in rule are matched.
The minimum thresholds can be modified as needed for the environment and severity level.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center