Memory Usage Test

This test reports statistics related to the usage of the physical memory of the system.

Target of the test : Any host system

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every server being monitored

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	The host for which the test is to be configured.
Useglance	This flag applies only to HP-UX systems. HP GlancePlus/UX is Hewlett-Packards’s online performance monitoring and diagnostic utility for HP-UX based computers. There are two user interfaces of GlancePlus/UX -- Glance is character-based, and gpm is motif-based. Each contains graphical and tabular displays that depict how primary system resources are being utilized. In environments where Glance is run, the eG agent can be configured to integrate with Glance to pull out detailed metrics pertaining to the memory usage of the HP-UX systems that are being monitored. By default, this integration is disabled. This is why the useglance flag is set to No by default. You can enable the integration by setting the flag to Yes. If this is done, then the test polls the Glance interface of HP GlancePlus/UX utility to report the detailed diagnosis information pertaining to memory usage.
Dynamic Memory Enabled	This flag applies only to the host system that is provisioned from a Microsoft Hyper-V Hypervisor. By default, this flag is set to No. If this flag is set to Yes, then, the eG agent will be able to pull out additional metrics pertaining to the memory usage of the host system provided, Dynamic Memory feature is enabled on the Microsoft Hyper-V Hypervisor through which the host system was provisioned.
Group Processes with Argument	By default, this parameter is set to No indicating that this test groups processes of an application only based on their names to list top-10 process groups that consumed memory resources excessively in the detailed diagnosis of the Used physical memory measure. If it is set to Yes, then, this test groups the processes with arguments that are passed to them.
High Security	This flag is applicable only when the target Linux host is monitored in the agentless manner. In highly secure environments, eG Enterprise could not perform agentless monitoring on a Linux host using SSH. To enable monitoring of the Linux hosts in such environments, set the HIGH SECURITY flag to Yes. It indicates that eG Enterprise will connect to the target Linux host in a more secure way and collect performance metrics. By default, this flag is set to No.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test

Measurement

Description

Measurement Unit

Interpretation

Total memory

Indicates the total physical memory of the system.

Used memory

Indicates the used physical memory of the system.

Free memory

Memory that does not contain any valuable data, and that will be used first when processes, drivers or Operating System need more memory. This does not include standby memory.

This measure typically indicates the amount of memory available for use by applications running on the target host.

On Unix operating systems (AIX and Linux), the operating system tends to use parts of the available memory for caching files, objects, etc. When applications require additional memory, this is released from the operating system cache. Hence, to understand the true free memory that is available to applications, the eG agent reports the sum of the free physical memory and the operating system cache memory size as the value of the Free physical memory measure while monitoring AIX and Linux operating systems.

Memory utilized

Indicates the percent usage of physical memory.

Percent

Ideally, the value of this measure should be low. While sporadic spikes in memory usage could be caused by one/more rogue processes on the system, a consistent increase in this value could be a cause for some serious concern, as it indicates a gradual, but steady erosion of valuable memory resources. If this unhealthy trend is not repaired soon, it could severely hamper system performance, causing anything from a slowdown to a complete system meltdown.

You can use the detailed diagnosis of this measure to figure out which processes on the host are consuming memory excessively.

Cleanup automation status

Indicates the current status of automatic action.

The values that this measure can report and their corresponding numeric values are discussed in the table above:

Measure value	Numeric value
Not Required	1
Started	2
Running	3
Completed	4
Not Enabled	5
Failed	6

Note:

By default, this measure reports the Measure Values listed in the table above. In the graph of this measure however, the value of this measure is represented using their numeric equivalents only.

Use the detailed diagnosis of this measure to find out what are the automation actions triggered when the memory utilization exceeds the value specified against the Automation Memory Limit parameter.

Note:

While monitoring Linux/AIX operating systems, you may observe discrepancies between the value of the Physical memory utilized measure and the memory usage percentages reported per process by the detailed diagnosis of the same measure. This is because, while the Physical memory utilized measure takes into account the memory in the OS cache of the Linux/AIX operating system, the memory usage percent that the detailed diagnosis reports per process does not consider the OS cache memory.