Citrix XenServer 6 Operating System Available MegaBytes Memory Monitor
This monitor checks the Available MBytes (Memory\% Available MBytes) for the system. If you receive an alert from this monitor, action can be required in order to bring the system back to an operational state..
The amount of available physical memory can become low under the following circumstances:
Too many applications/processes are running simultaneously on the computer.
An application may be leaking memory over time.
To address a low physical memory condition an administrator may choose one or more of the following options:
Stop or kill one or more applications, daemons, or processes. Execute the "top" command or execute "Top 10 CPU Processes" Task from the State View. It will provide a listing of processes ordered by CPU usage, the listing by default will display only the top CPU consuming processes and their corresponding PID (Process ID). Utilizing the output from the "top" command identify any offending or unnecessary processes along with its PID number. Issue a "kill" command utilizing the PID for the process. For example, if the PID number for the process is 4510, then issue the command 'kill 4510'. You can verify that available memory has been increased by running the "Memory Information" Task from the State View.
Add additional Physical Memory to the computer.
Move applications to one or more additional servers.
You can view Available Memory by running the "Memory Info" Task from the State View.
VMStat provides detailed Memory Statistics averaged since the last reboot. You can run the VMStat Task from the State View.
| Target | Microsoft.Linux.XenServer.6.OperatingSystem | ||
| Parent Monitor | System.Health.PerformanceState | ||
| Category | PerformanceHealth | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | Microsoft.Unix.WSMan.Performance.Average.Threshold.MonitorType | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home<UnitMonitor ID="Microsoft.Linux.XenServer.6.OperatingSystem.AvailableMBytes.Monitor" Accessibility="Public" Target="Microsoft.Linux.XenServer.6.OperatingSystem" TypeID="Unix!Microsoft.Unix.WSMan.Performance.Average.Threshold.MonitorType" Enabled="true" ParentMonitorID="SystemHealth!System.Health.PerformanceState">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="Microsoft.Linux.XenServer.6.OperatingSystem.AvailableMBytes.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Value$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState HealthState="Error" MonitorTypeStateID="UnderThreshold" ID="UnderThreshold"/>
<OperationalState HealthState="Success" MonitorTypeStateID="OverThreshold" ID="OverThreshold"/>
</OperationalStates>
<Configuration>
<TargetSystem>$Target/Host/Property[Type="Unix!Microsoft.Unix.Computer"]/NetworkName$</TargetSystem>
<Uri>http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_MemoryStatisticalInformation?__cimnamespace=root/scx</Uri>
<Filter/>
<SplitItems>true</SplitItems>
<Interval>300</Interval>
<ObjectName>Memory</ObjectName>
<CounterName>Available MBytes</CounterName>
<InstanceName/>
<Value>$Data///*[local-name()="AvailableMemory"]$</Value>
<Threshold>2.5</Threshold>
<NumSamples>3</NumSamples>
</Configuration>
</UnitMonitor>