Memory: Working Set Usage (in Bytes)

ComTrade.EMC.Documentum.Windows.ContentServer.MemoryWorkingSetUsageMonitor (UnitMonitor)

Monitors the memory: working set usage (in Bytes) of the Content Server service process, without the dmbasic Method Server and Agent Exec processes.

Knowledge Base article:

Summary

This monitor checks the Content Server memory working set usage in Bytes.

The working set of a process is the set of pages in the virtual address space of the process that are currently resident in physical memory. The working set contains only pageable memory allocations; nonpageable memory allocations, such as Address Windowing Extensions (AWE) or large page allocations are not included in the working set.

The working set of a program is a collection of those pages in its virtual address space that have recently been referenced.

It includes both shared and private data. The shared data includes pages that contain all instructions your application executes, including those in your DLLs and system DLLs. As the working set size increases, memory demand increases.

Configuration

The following configuration parameters are customizable:

Element properties:

TargetComTrade.EMC.Documentum.Windows.ContentServer
Parent MonitorSystem.Health.PerformanceState
CategoryPerformanceHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeComTrade.EMC.Documentum.Windows.Service.ConsecutiveSamplesThreshold.ErrorOnTooHigh
RemotableTrue
AccessibilityPublic
Alert Message
Content Server Process Memory: Working Set Usage Threshold Exceeded
Memory: Working set usage {0} for the content server service {1} is greater that the predefined threshold.

Value: {2}
Repository Name: {3}
Server Name: {4}
RunAsDefault

Source Code:

<UnitMonitor ID="ComTrade.EMC.Documentum.Windows.ContentServer.MemoryWorkingSetUsageMonitor" Accessibility="Public" Enabled="true" Target="CTDmWinDisc!ComTrade.EMC.Documentum.Windows.ContentServer" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="ComTrade.EMC.Documentum.Windows.Service.ConsecutiveSamplesThreshold.ErrorOnTooHigh" ConfirmDelivery="true">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="ComTrade.EMC.Documentum.Windows.ContentServer.MemoryWorkingSetUsageMonitor_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/SampleValue$</AlertParameter1>
<AlertParameter2>$Target/Property[Type="CTDmWinDisc!ComTrade.EMC.Documentum.Windows.ContentServer"]/ServiceName$</AlertParameter2>
<AlertParameter3>$Data/Context/SampleValue$</AlertParameter3>
<AlertParameter4>$Target/Property[Type="CTDmLib!ComTrade.EMC.Documentum.ContentServer"]/RepositoryName$</AlertParameter4>
<AlertParameter5>$Target/Property[Type="CTDmWinDisc!ComTrade.EMC.Documentum.Windows.ContentServer"]/ServiceName$</AlertParameter5>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="SampleCountTooHigh" MonitorTypeStateID="SampleCountTooHigh" HealthState="Warning"/>
<OperationalState ID="SampleCountNormal" MonitorTypeStateID="SampleCountNormal" HealthState="Success"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<ServiceName>$Target/Property[Type="CTDmWinDisc!ComTrade.EMC.Documentum.Windows.ContentServer"]/ServiceName$</ServiceName>
<ObjectName>Documentum CS Process</ObjectName>
<CounterName>Memory: Working Set (in Bytes)</CounterName>
<InstanceProperty>$Target/Property[Type="CTDmLib!ComTrade.EMC.Documentum.ContentServer"]/RepositoryName$.$Target/Property[Type="CTDmLib!ComTrade.EMC.Documentum.ContentServer"]/ServerConfigName$</InstanceProperty>
<ValueProperty>WorkingSet</ValueProperty>
<Frequency>600</Frequency>
<Threshold>900000000</Threshold>
<NumSamples>2</NumSamples>
</Configuration>
</UnitMonitor>