To install monitors for collecting performance data and for enabling event management, system administrators should follow the recommended process of incrementally creating monitors in a development environment and testing before moving to a production environment. Each workflow illustrates the process steps discussed in the table that follows.
This process assumes you have already planned the deployment, installed the Infrastructure Management system, and configured Infrastructure Management components.
For information about setting up this environment, see Staging Integration Service host deployment and policy management for development, test, and production best practices.
Tip
Review the Monitoring configuration best practice reference before proceeding with this process.
Keep the following guidelines in mind during the configuration process:
Step | Task | Reference |
---|---|---|
1 | Establish a policy naming convention and policy precedence scheme before you begin creating policies. | Monitoring policy naming standards and definition best practices Policy precedence best practices
|
2 | Create separate staging policies in Central Monitoring Administration for the Infrastructure Management development, test, and production environments assigned to the appropriate Integration Service instances. Tip: Develop a clear strategy for assigning the PATROL Agents to each Integration Service. The Infrastructure Management Server does not auto-balance the load between PATROL Agents and Integration Services so the initial assignment is important. Although at least one Integration Service must exist per network, within the network a convention based on name or function, or simply round-robin assignment is acceptable as long as you are consistent and keep track in order to avoid overloading any one Integration Service. | |
3 | Create PATROL Agent/KM deployable packages for test PATROL Agents and KMs in the Central Monitoring Administration repository, but do not deploy them to production at this point in the process. Note If previous versions of PATROL Agents already exist, the packages must be configured to install into the same directory as the existing PATROL Agent. Best practices
| |
4 | Deploy the PATROL Agent or KM deployable package to the development or test managed servers, and run the PATROL packages silent installer on the test managed machines.. | Downloading and installing an installation package
|
5 | Validate that the PATROL deployable package installations were successful. | none |
6 | Validate and test the PATROL Agents in Central Monitoring Administration. | Viewing the status of Infrastructure Management components in Central Monitoring Administration |
7 | Configure global server thresholds for the monitoring solutions (KMs) in Central Monitoring Administration. Best practice Identify and configure the thresholds to set at the PATROL Agent and monitoring solution level. See Threshold considerations. | |
8 | In Central Monitoring Administration, create monitoring policies to be tested in the development environment. Best practices
| Creating or editing a monitoring policy |
9 | (Optional) If you are creating blackout policies, create time frames for the monitoring solutions (KMs) in Central Monitoring Administration. | |
10 | (Optional) Create blackout policies for the monitoring solutions (KMs) in Central Monitoring Administration. | |
11 | Enable the policies for the monitoring solutions (KMs) in Central Monitoring Administration. | |
12 | Test and validate that data is collected according to the policies you defined. Resolve any issues.
Note Integrate data collection and event sources in specific groups one at a time, and then observe performance of the Infrastructure Management components after each group is integrated. For example, integrate all monitoring for a specific application and then observe and tune the Infrastructure Management components for performance, if needed, before integrating additional collection. Leverage the self-monitoring for performance in the Infrastructure Management Server. As each group is integrated, review the configuration report to verify that the number of devices, instances, and parameters does not exceed the plan. Tune as needed. | Managing and monitoring events
|
Step | Task | Reference |
---|---|---|
13 | Move the validated policies from test to production leveraging the export/import utility. | Exporting and importing blackout and monitoring policies |
14 | Deploy the PATROL packages to a subset of production machines.
| |
15 | Deploy the PATROL Agent or KM deployable package to the production managed servers, and run the PATROL packages silent installer on the production managed machines.
| Downloading and installing an installation package
|
16 | Validate that the PATROL deployable package installations were successful. | none |
17 | Validate and test the PATROL Agents are in the Central Monitoring Administration. | none |
18 | Enable the policies in production. | Enabling or disabling a monitoring policy |
19 | Validate agents and data collection in production. Resolve any issues. | Viewing the status of Infrastructure Management components in Central Monitoring Administration |
20 | Deploy remaining agents in batches.
| none |
21 | Between each batch of PATROL Agents and Integration Services deployed and configured, ensure that the Infrastructure Management Server and Integration Services are performing well and can still manage the load. Performance diagnostics are available in the operator console for the Infrastructure Management Server and the respective remote agent nodes where the Integration Service is running. Ensure that the scalability limitations of the Integration Services are not exceeded. | Performance benchmarks and tuning
|
Monitoring capability | Reference |
---|---|
Define manual application models based on groups and devices, or implement BMC TrueSight App Visibility manager to enable automatic application models from which you can monitor the performance and health of active or synthetic applications, perform diagnostics, and trace application transactions. | Use case: Monitoring the infrastructure in the context of an application |
Use Third-party adapters to provide a mechanism for external applications to funnel data into Infrastructure Management. Data adapters facilitate the synchronization of performance data collected by specific monitoring solutions into Infrastructure Management for further analysis. | |
Define impact service models to monitor when higher-level entities, such as applications, technical services, business services, and organizations are impacted, and how they are impacted when lower-level IT infrastructure entities, such as servers, network devices, and application systems are affected by some condition. | Configuring business services and other CIs to appear in the Applications page |
See also Integrating.
Navigating the Central Monitoring Administration interface