This monitor catches Xian events that notifies when the Storage used has changed its state.
Storage used is over threshold.
The storage used is above the maximum threshold configured in Xian Network Manager 2012.
The allocated storage (disk partitions, file systems, RAM "for some architectures, this is further segmented into regular memory, extended memory, and so on", backing store for virtual memory "swap space") has exceeded expected values, reducing available space.
Check the minimum memory size set and make sure it is sufficient. If large memory usage was due to a normal event, the solution is to install more memory. If it is due to a rare or abnormal event, fix the related problem.
Monitors the amount of allocated storage.
Target | Jalasoft.Xian.Common.Elements.ThirdParty.Nokia.JsXNokiaFirewallHRStorageElement | ||
Parent Monitor | System.Health.PerformanceState | ||
Algorithm | WorstOf | ||
Category | StateCollection | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | MatchMonitorHealth | ||
Alert Priority | Low | ||
Alert Auto Resolve | True | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
|
<AggregateMonitor ID="Jalasoft.Xian.SmartManagementPacks.NokiaFirewalls.StorageUsed.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_Nokia!Jalasoft.Xian.Common.Elements.ThirdParty.Nokia.JsXNokiaFirewallHRStorageElement" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="StorageUsed_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>