|
Default Parameters for VmgOSMemoryTest
Memory shortage on a VM can affect the memory allocation to crucial processes that are being executed on the VM, which in turn can adversely impact the performance of the applications running on the VM. One of the primary reasons for Memory shortage is that of precious memory space being unnecessarily hogged by Modified and Standby memory lists that hold temporary/unused data. The Modified and Standby memory lists cache temporary data when the applications/services run in the VM. These temporary data will no longer be used by the applications/services thus hogging memory space unnecessarily. Therefore, administrators should clear the cached data on a regular basis. If the cached data is not cleared regularly, sometimes, you may not be able to allocate memory to the business-critical processes, which will seriously impact service/application delivery and impair user experience. Therefore, it is imperative that you should closely observe if the memory shortage occurs due to data growth of the Modified and Standby memory lists and proactively initiate remedial actions before it causes severe memory contention on the VM. This can be achieved with the help of the VmgOSMemoryTest.
This test auto discovers the VMs on the virtual server and periodically monitors the memory usage of each VM, checks whether adequate physical memory is available to the VM, and if not, promptly alerts users to the same. In the process, the test also reveals the VMs on which the memory space is abnormally hogged by Modified or Standby memory list. This way, VMs that experience potential memory contention are brought to your attention. Besides warning you of memory contention that Modified/Standby memory lists can cause, the test also empowers you to avoid probable memory shortage by initiating automated actions. These automated actions can be closely tracked using detailed diagnostics.
This page depicts the default parameters that need to be configured for the VmgOSMemoryTest.
Administrators of some high security environments might not have permissions to internally monitor one/more VMs. The eG agent can be configured to not obtain the ‘inside view’ of such ‘inaccessible’ VMs using the IGNORE VMS INSIDE VIEW parameter. Against this parameter, you can provide a comma-separated list of VM names, or VM name patterns, for which the inside view need not be obtained. For instance, your IGNORE VMS INSIDE VIEW specification can be: *ubuntu*,*lin*,rhel*,*suse*. Here, the * (asterisk) is used to denote leading and trailing spaces (as the case may be). By default, this parameter is set to none indicating that the eG agent obtains the inside view of all VMs on a QVD host by default.
Note:
While performing VM discovery, the eG agent will not discover the operating system of the VMs configured in the IGNORE VMS INSIDE VIEW text box.
Administrators of some virtualized environments may not want to monitor some of their less-critical VMs - for instance, VM templates - both from ‘outside&rsquo and from ‘inside’. The eG agent in this case can be configured to completely exclude such VMs from its monitoring purview. To achieve this, provide a comma-separated list of VMs to be excluded from monitoring in the EXCLUDE VMS text box. Instead of VMs, VM name patterns can also be provided here in a comma-separated list. For example, your EXCLUDE VMS specification can be: *ubuntu*,*lin*,rhel*,*suse*. Here, the * (asterisk) is used to denote leading and trailing spaces (as the case may be). By default, this parameter is set to none indicating that the eG agent obtains the inside and outside views of all VMs on a virtual host by default. By providing a comma-separted list of VMs/VM name patterns in the EXCLUDE VMS text box, you can make sure the eG agent stops collecting ‘inside’ and ‘outside’ view metrics for a configured set of VMs.
By default, this test connects to each virtual guest remotely and attempts to collect “inside view” metrics. In order to obtain a remote connection, the test must be configured with user privileges that allow remote communication with the virtual guests. For this, you need to specify a DOMAIN name, an ADMIN USER name, and an ADMIN PASSWORD. Since QVD supports only Linux guests, specify “none” in the DOMAIN field, and specify a local administrator account name in the ADMIN USER text box.
Prior to this, you need to ensure that the same local administrator account is available or is explicitly created on each of the virtual machines to be monitored. Then, proceed to provide the password of the ADMIN USER against ADMIN PASSWORD, and confirm the password by retyping it in the CONFIRM PASSWORD text box.
If key-based authentication is implemented between the eG agent and the SSH daemon of a Linux guest, then, in the ADMIN USER text box, enter the name of the user whose <USER_HOME_DIR> (on that Linux guest) contains a .ssh directory with the public key file named authorized_keys. The ADMIN PASSWORD in this case will be the passphrase of the public key; the default public key file that is bundled with the eG agent takes the password eginnovations. Specify this as the ADMIN PASSWORD if you are using the default private/public key pair that is bundled with the eG agent to implement key-based authentication. On the other hand, if you are generating a new public/private key pair for this purpose, then use the passphrase that you provide while generating the pair. For the detailed procedure on Implementing Key-based Authentication refer to the Monitoring Quality Virtual Desktop document.
While monitoring virtualized desktop environments, the REPORT BY USER flag is set to YES by default; which implies that in case of VDI servers, by default, the guests will be identified using the login of the user who is accessing the guest OS. In other words, in VDI environments, this test will, by default, report measures for every username_on_virtualmachinename.
The REPORT POWERED OS flag becomes relevant only if the REPORT BY USER flag is set to ‘Yes’.
If the REPORT POWERED OS flag is set to Yes (which is the default setting), then this test will report measures for even those VMs that do not have any users logged in currently. Such guests will be identified by their virtual machine name and not by the username_on_virtualmachinename. On the other hand, if the REPORT POWERED OS flag is set to No, then this test will not report measures for those VMs to which no users are logged in currently.
Typically, when performing VM discovery, the eG agent automatically discovers the operating system on which every VM runs, and all the IP addresses that each VM supports. If two are more VMs on a target vSphere server are in a VM cluster, then the eG agent will also auto-discover the cluster IP address. Since the cluster IP address is shared by all VMs in the cluster, this IP address will be in the discovery list of every VM in the cluster. In this case, if the eG agent attempts to obtain the 'inside view' of each VM in a cluster using their cluster IP address, incorrect metrics may be reported sometimes. To avoid this, you may want to instruct the eG agent to not use the cluster IP address when collecting 'inside view' metrics. For this, specify a comma-separated list of cluster IP addresses to be excluded in the EXCLUDE IP text box.
By default, the detailed diagnosis of the Used physical memory measure of this test reports the number of instances of each process running on the VM, and the aggregated memory usage (in MB and %) of every process across all its instances. For example, if users to a VM are together having 15 instances of Chrome open on the machine at around the same time, then the detailed diagnosis of the Used physical memory measure will compute and display the collective memory usage of all 15 instances against the Application Name, Chrome. From this, you can quickly identify the exact process that is ‘collectively’ (i.e., across its instances) over-utilizing the memory. Sometimes, administrators might want to isolate not just the process, but also similar process arguments that are guilty of abnormal memory consumption. This granular insight will take administrators closer to the root-cause of the memory bottleneck on a desktop. For instance, in the Chrome example above, say 8 of the 15 instances are used to access the same YouTube video, and 7 instances are accessing a shopping site. In such a case, if memory usage is aggregated at the URL-level and not the process-level, then administrators can quickly identify which precise URL is draining memory - the YouTube video? or the shopping site? For this, detailed diagnostics should be grouped by process arguments (eg., URLs) and not just by process/application names. To enable grouping by arguments, set the GROUP PROCESSES WITH ARGUMENTS flag to Yes. By default, this flag is set to No.
By default, MEMORY UTILIZATION IN PERCENT parameter is set to 75 percentage indicating that by default this test will display top-10 memory intensive processes on a VM in the detailed diagnosis of the Physical memory utilized measure only when the memory utilization reaches/exceeds 75 percentage. On the other hand, if the memory utilization is lower than the value specified against this parameter, then, this test displays only topv3 memory intensive processes in the detailed diagnosis of the Physical memory utilized measure so as to conserve storage space on the database. However, this setting can be overridden if required.
A memory shortage caused due to memory space hogged by modified and standby memory lists has become an increasingly frequent and critical problem. The memory shortage can make a server stutter or run more slowly than usual. Such operational interruptions can make you spend more time on waiting for pages and programs to load, disturbing your work flow and leading to work delays. Moreover, memory shortage can not only impair user productivity, but can also bring crucial business processes to a halt, and can severely degrade overall user experience with the server. To avoid such an outcome, administrators need to rapidly empty the memory space unnecessarily hogged by the modified and standby memory lists. This way, administrators can ensure that adequate memory is always available for executing business-critical processes.
To enable administrators to achieve this, eG Enterprise offers ‘Automation Actions’. These actions are governed by the ‘Automation Action Enabled’ flag.
AUTOMATED ACTION ENABLED flag, if enabled, automatically initiates user-configured actions, so that the memory hogged by modified and standby memory lists can be cleared when memory utilization crosses a configured limit.
Note:
The ‘Automation Action Enabled’ parameters, once configured, will apply only to the chosen component. These settings will not be applied to other components even if the Apply to other components button is clicked in the Specific Test Configuration page.
EMPTY MODIFIED MEMORY flag appears only if the Automated Action Enabled flag is enabled.
Modified memory contains cached data and code that is not actively in use by processes, the system and the system cache. This memory needs to be written out before it will be available for allocation to a process or for system use. You can easily clear this memory using the EMPTY MODIFIED MEMORY flag.
By default, EMPTY MODIFIED MEMORY flag is set to No. When this flag is set Yes, amount of memory assigned to the modified list will be automatically cleared if the memory utilization reaches/exceeds the value specified against the Automation Memory Limit parameter.
EMPTY STANDBY MEMORY flag appears only if the Automated Action Enabled flag is enabled.
Standby memory is a page of physical memory that is not actively used. When writing a series of frequently used information in the memory area, the programs and services running on the server will use part of memory as cache. The cache should be released and made available after executing programs and services. If the standby memory is not cleared on a regular basis, it can slow down the server operations. Therefore, it is necessary to clear the standby memory at regular intervals. This can easily done using the EMPTY STANDBY MEMORY flag.
By default, EMPTY STANDBY MEMORY flag is set to No. When this flag is set Yes, memory that is allocated to the standby page list will be automatically cleared if the memory utilization reaches/exceeds the value specified against the Automation Memory Limit parameter.
AUTOMATION MEMORY LIMIT flag appears only if the Automated Action Enabled flag is enabled.
In AUTOMATION MEMORY LIMIT text box, specify the upper limit for memory utilization in percentage beyond which this test should trigger user-configured automation actions. By default, 95 percentage is set against this parameter. When the memory utilization reaches/exceeds the value specified in this text box, the user-configured actions will be automatically triggered. However, you can override this settings if required.
The 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.
When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz” and $port will be changed to “80” when configuring a test.
|