HP Matrix Operating Environment Software manual How memory usage is calculated

Page 12

can be copied and edited to quickly create a new, similar templates, or you can create a completely new template that contains no predetermined settings.

Application template storage

Template attributes are stored in the System Insight Manager database on the CMS.

Application template recognition

Application Discovery recognizes the uniqueness of a template based on its name and its version, and informs you when you try to use a name and version combination that is already in use by another application template.

NOTE:

Supplied templates are stored in the Matrix Operating Environment database. For information about this database, see the Matrix Operating Environment installation guides for HP-UX or Microsoft Windows operating systems.

How memory usage is calculated

Processes have private memory, which is owned privately by each process, and they have shared memory. Shared memory can be shared (in theory) with none, one, some, or all other processes on the same system.

In Application Discovery memory calculations are made for matched applications and displayed in the detail screen of a host.

Figure 3 Memory usage by application as shown in Application Discovery

In Application Discovery, application memory shown is the sum of all private memory in use by all the processes in that application and the sum of all shared memory in use by all the processes in that application. That is, shared memory is displayed as though it is not shared. This means that the totals shown for memory usage are an overstated approximation of actual memory usage for any particular application.

Here is why accurately summing memory shared among processes is difficult to do:

•The degree of sharing among processes is unknown. For a given process, the shared memory can be shared with every process on the system, only some processes on the system, only some processes within the application, or with all of the processes within the application.

•The 'right' answer for how to sum shared memory for processes depends in part on how the individual administrator uses the information for planning. For example, is the administrator thinking of adding an application instance to the host? Is he or she thinking of moving an application instance to another host? Is the administrator thinking of moving the entire application to another host?

To arrive at a usable deterministic answer, all the shared memory for each process is summed. This conservative calculation should allow you to safely estimate resource usage for the applications shown.

Understanding server resource consumption

Application Discovery consumes varying amounts of server resources as it goes about its work of discovering application and system data for display and storage. To monitor this resource usage, select the Admin/Config tab and then the AD Server tab.

12 Components and concepts

Page 11 Page 13
Image 12
Page 11 Page 13
Contents Application Discovery 7.2 User Guide Page Contents Troubleshooting Support and other resourcesError messages Completing certificate exchange Configuring the Wbem provider password Glossary IndexDocumentation feedback Key to event attributesPage Features of Application Discovery IntroductionIntroduction Components and concepts Application Discovery componentsRefining Application Discovery How discovery worksUnderstand your current discovery state Discovery ratioUnderstanding application templates Refine discovery by checking agent stateRefine discovery by creating application templates Warm-up ratioHow memory usage is calculated Understanding server resource consumptionUsed mem Page Procedures and examples Using System Insight Manager to start the agentStarting the agent from the command line Starting Application DiscoveryReconfigure a running agent from the command line Using System Insight Manager to stop the AD agentStopping the agent from the command line Checking agent stateAdjusting the user interface Working with data viewsExplanation of agent states Set screen data refresh intervalChange the data view Set color themeSet number of table rows Sort data in view tablesFilter data in view tables Other controls available from right-clicking on a view tableNavigate between views Set visibility for hosts on Application Discovery screensSet visibility for matched applications Modifying the maximum size of an event list Set visibility for packages on Application Discovery screensSetting event attributes Setting data polling intervalIntroduction to event settings in Application Discovery Setting event severity Setting alert locationManaging application templates Find an application templateChange application template values Create a new template Key to application template values Application identity and system scope fieldsUsr/sbin/biod Separation rule fields and their descriptions OSverUser scope Create an application template rule Aggregation rule fields and their descriptionsCreate a process aggregation rule Managing application templates Procedures and examples Managing application templates How to remove types from the aggregation rule Check unmatched processes to find application candidatesUnderstanding the tables that show unmatched processes Filling in the system scope fields using table data Filling in the aggregation rule fields using table dataFilling in the template separation rule fields Create an application workload in HP Matrix OE visualization Backing up Application Discovery files Page Troubleshooting Errors in installationData missing in Application Discovery screens Applications not visible in Application Discovery screens Host not visible in Application Discovery screens Data missing in Application Discovery screens Packages not visible in Application Discovery screens Page Go to /var/opt/amgr/procmaps Errors in Application Discovery user interface operation UI Unable to connect to servermessagesJava UI exception message displays To fix this error, do one of the following On the managed nodes, run the command How to contact HP Subscription serviceSupport and other resources Information to collect before contacting HPHP authorized resellers Related informationDocuments ResourcesTypographic conventions Computer outputPage Documentation feedback Page Page Amgrd OptionsInstallation NodaemonAuthors Agentconfig Amx -cOpt/amgr/bin/agentconfig Agentconfig file Opt/amgr/bin/amgrd Key to event attributes Event typesEvent severity types Additional event types specific to Application DiscoveryEvent viewing locations Error messages Error messages seen when trying to logPage Completing certificate exchange from the command line Completing certificate exchangeIntroduction Completing certificate exchange Configuring the Wbem provider password Page Glossary ApplicationOperating system referred to as a guest OS See also system Wbem Agentwbemcleanup command IndexCmdline Path Pid scope Title
Related manuals
Manual 111 pages 21.04 Kb Manual 12 pages 7.25 Kb

Matrix Operating Environment Software specifications

HP Matrix Operating Environment (MOE) is an innovative software platform designed to deliver efficient management and orchestration of IT resources across physical, virtual, and cloud infrastructures. It provides a comprehensive solution for organizations that require a robust and flexible environment to manage their IT operations seamlessly.

One of the main features of HP MOE is its ability to optimize resource utilization by automating the provisioning and management of infrastructure components. This includes the ability to rapidly deploy servers, storage, and networking resources in a manner that meets the dynamic needs of modern businesses. This automation significantly reduces the time and effort required for manual configurations, enabling IT teams to focus on strategic initiatives rather than routine tasks.

The software offers a unified management interface that provides visibility into the entire IT environment. Users can monitor performance metrics, track resource allocation, and manage workflows through a single dashboard. This centralized control not only simplifies operations but also enhances decision-making capabilities by providing real-time insights into system health and performance.

Another critical characteristic of HP MOE is its support for both physical and virtual resources. The platform is designed to seamlessly integrate with existing infrastructure, making it easier for organizations to adopt virtualization and hybrid cloud strategies. Its compatibility with industry-standard hypervisors allows businesses to leverage their current investments while taking advantage of the benefits of virtualization.

HP MOE incorporates advanced technologies such as automation scripts, APIs, and tools for workload balancing. This technological backbone enables organizations to implement elasticity in their environments, allowing them to scale resources up or down based on demand. The software also supports a service-oriented architecture, facilitating integration with other enterprise applications and systems.

Security is a top priority in the design of HP MOE. The software provides robust security features that ensure data integrity and protect against unauthorized access. This includes role-based access controls, encryption, and compliance reporting, all of which contribute to a secure operating environment.

In summary, HP Matrix Operating Environment Software is a powerful solution that addresses the complexities of managing modern IT resources. Its key features include automation, unified management, support for physical and virtual environments, and strong security measures. With its ability to enhance efficiency and streamline operations, HP MOE is an essential tool for organizations looking to stay competitive in an increasingly digital landscape.
Top Page Image Contents