HP Matrix Operating Environment Software Filling in the system scope fields using table data

Page 35

Figure 16 Example “unmatched processes” table

You can sort or filter this table to find processes with which you want to define an application.

TIP:

One way to reduce the amount of “noise” cluttering your tables is to create a template that collects “uninteresting” processes into an application that can be hidden.

Filling in the system scope fields using table data

In the following image, you can see the columns directly relevant to the System Scope fields in an application template (dark gray column headings). By entering a specific operating system (OS), operating system version (OSver), and/or architecture (Arch), you can limit the application of the template to particular systems in your network.

Figure 17 Finding data to enter in system scope area of application template

For more details about this part of an application template, see “Application identity and system scope fields and their descriptions” (page 27) .

Filling in the template separation rule fields

In the following image, you can see the columns indirectly relevant to the Separation Rules fields in an application template – pid, ppid, user, sid, and ct. These columns are indirectly relevant because you do not use the actual values in the columns to define the separation rule. Instead, this information is provided to help you decide which attributes are appropriate to select.

For example, when viewing the data in the table, look at the relationships among process IDs, users, and sessions to determine what relationships you want to define in the Separation Rules.

Figure 18 Finding data to enter into Separation Rule fields

For details about setting attributes in an application template, see “Separation rule fields and their descriptions” (page 28) .

Filling in the aggregation rule fields using table data

In the following image, you can see the columns directly relevant to the Aggregation Rule fields in an application template. By entering one or more users (User), groups (Group), paths (Path), and/or arguments (Cmdline), you can limit the application of the template to particular processes running in your network.

Managing application templates 35

Page 34 Page 36
Image 35
Page 34 Page 36
Contents Application Discovery 7.2 User Guide Page Contents Support and other resources TroubleshootingKey to event attributes Error messages Completing certificate exchangeConfiguring the Wbem provider password Glossary Index Documentation feedbackPage Introduction Features of Application DiscoveryIntroduction Application Discovery components Components and conceptsDiscovery ratio Refining Application DiscoveryHow discovery works Understand your current discovery stateWarm-up ratio Understanding application templatesRefine discovery by checking agent state Refine discovery by creating application templatesUnderstanding server resource consumption How memory usage is calculatedUsed mem Page Starting Application Discovery Procedures and examplesUsing System Insight Manager to start the agent Starting the agent from the command lineChecking agent state Reconfigure a running agent from the command lineUsing System Insight Manager to stop the AD agent Stopping the agent from the command lineSet screen data refresh interval Adjusting the user interfaceWorking with data views Explanation of agent statesSort data in view tables Change the data viewSet color theme Set number of table rowsOther controls available from right-clicking on a view table Filter data in view tablesSet visibility for matched applications Navigate between viewsSet visibility for hosts on Application Discovery screens Set visibility for packages on Application Discovery screens Modifying the maximum size of an event listIntroduction to event settings in Application Discovery Setting event attributesSetting data polling interval Find an application template Setting event severitySetting alert location Managing application templatesChange application template values Create a new template Application identity and system scope fields Key to application template valuesUsr/sbin/biod OSver Separation rule fields and their descriptionsUser scope Create a process aggregation rule Create an application template ruleAggregation rule fields and their descriptions Managing application templates Procedures and examples Managing application templates Understanding the tables that show unmatched processes How to remove types from the aggregation ruleCheck unmatched processes to find application candidates Filling in the template separation rule fields Filling in the system scope fields using table dataFilling in the aggregation rule fields using table data Create an application workload in HP Matrix OE visualization Backing up Application Discovery files Page Errors in installation TroubleshootingData 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 UI Unable to connect to servermessages Errors in Application Discovery user interface operationJava UI exception message displays To fix this error, do one of the following On the managed nodes, run the command Information to collect before contacting HP How to contact HPSubscription service Support and other resourcesResources HP authorized resellersRelated information DocumentsComputer output Typographic conventionsPage Documentation feedback Page Page Options AmgrdNodaemon InstallationAuthors Amx -c AgentconfigOpt/amgr/bin/agentconfig Agentconfig file Opt/amgr/bin/amgrd Event types Key to event attributesEvent viewing locations Event severity typesAdditional event types specific to Application Discovery Error messages seen when trying to log Error messagesPage Introduction Completing certificate exchange from the command lineCompleting certificate exchange Completing certificate exchange Configuring the Wbem provider password Page Application GlossaryOperating system referred to as a guest OS See also system Wbem Index Agentwbemcleanup commandCmdline 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