Nokia Firewall: Processor load Health Monitor

Jalasoft.Xian.SmartManagementPacks.NokiaFirewalls.ProcessorLoad.1.1 (AggregateMonitor)

This monitor catches Xian events that notifies when the Processor load has changed its state.

Knowledge Base article:

Summary

Processor load is over threshold.

The average, over the last minute, of the processor time percentage loaded is above the maximum threshold configured in Xian Network Manager 2012.

Causes

If the percentage exceeds 75% for continuous periods, you may have a processor bottleneck on your device. Occasional spikes of 100% are nothing to worry about and are normal for most servers.

Resolutions

If you notice that the percentage is gradually increasing, it is a sign that you might eventually run out of processor cycles on your device. In order to overcome a bottleneck you can also: get additional processors, get processors with a larger cache, tune your queries to reduce the processor load, tune your application so that it does not have to access the disk frequently, or move some of the processing load to another server.

Additional

Monitors the average, over the last minute, of the time percentage when Nokia Firewall processor was not idle.

Element properties:

TargetJalasoft.Xian.Common.Elements.ThirdParty.Nokia.JsXNokiaFirewallHRProcessorElement
Parent MonitorSystem.Health.PerformanceState
AlgorithmWorstOf
CategoryStateCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityLow
Alert Auto ResolveTrue
RemotableTrue
AccessibilityPublic
Alert Message
Processor load Alert
{0}

Source Code:

<AggregateMonitor ID="Jalasoft.Xian.SmartManagementPacks.NokiaFirewalls.ProcessorLoad.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_Nokia!Jalasoft.Xian.Common.Elements.ThirdParty.Nokia.JsXNokiaFirewallHRProcessorElement" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="ProcessorLoad_AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Low</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Params/Param[3]$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<Algorithm>WorstOf</Algorithm>
</AggregateMonitor>