The following high-level steps are required when deploying BMC PATROL collection with BMC ProactiveNet.
- Determine the type and volume of data to be collected.
- Determine the number of PATROL Agents, Integration Services, and BMC ProactiveNet Servers required.
- Configure and deploy PATROL Agents.
- Configure and deploy the PATROL Integration Services as required.
- Connect the Integration Services to the BMC ProactiveNet Server.
- Observe and confirm proper operation of the BMC ProactiveNet Server and Integration Services.
- Repeat steps 3-6 as required.
Recommendations for each step are provided in the following sections.
Determine the type and volume of data to be collected
- Determine what will be monitored in the environment and how that data will be used. Specifically identify from which systems, applications, and components in your environment you need performance metrics (and historic trend data), and from which components you will need events and alerts. This important step dictates the requirements for all steps that follow.
- The volume of data and events collected might be constrained by the amount of hardware or budget allocated so prioritize and categorize the data being collected to make it easier to adjust to any hardware or budget constraints.
Determine the number of PATROL Agents, Integration Services, and BMC ProactiveNet Servers required
- Understand the scaling and sizing requirements of the BMC ProactiveNet Server, Integration Service, and monitoring solutions. Reading and understanding the Performance and scalability recommendations is a prerequisite to deployment planning. These recommendations will help you decide how much can be collected overall, and whether data collection needs to be enabled or disabled at the monitoring solution level or at the PATROL Adapter level.
- Determine the location of all PATROL Agents and the respective Integration Services. At least one Integration Service must exist for each network, and generally the Integration Service must be closer to the PATROL Agents connecting to it. This requirement minimizes the number of connections to the BMC ProactiveNet Server and makes firewall management easier because there is one connection per Integration Service.
Develop a clear strategy for assigning the PATROL Agents to each Integration Service. The BMC ProactiveNet 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.
Configure and deploy PATROL Agents
- The monitoring solutions must be configured to collect only data which is needed from the central BMC ProactiveNet console or that is needed for event generation from thresholds. Collecting more data than this creates unwanted overhead on the Integration Service and BMC ProactiveNet Server.
- Ensure that only required instances are being discovered. Each monitoring solution may have different options on how to control this.
- Disable discovery of instances that are short lived (for example, instances that are created and then deleted within the span of one to two days).
- Ensure that all monitoring solutions used for data collection are preloaded, as collection with BMC ProactiveNet must not require console interaction.
- Consider whether high availability (HA) is needed for the PATROL Agents used for collection. If the agent is performing local collection on a host that provides some service, the agent might already be part of the host-level HA setup for the service or application on that host. However, if the PATROL Agent is performing remote collection, that agent must be configured for HA.
If the agent running on a VMware virtual machine (VM), VMware high availability is a recommended option.
- Patrol Agent devices must be named using a fully qualified domain name (FQDN) to ensure proper consolidation of devices on the BMC ProactiveNet Server (BMC PATROL Agent variable: AgentSetup/integration/publishHostName). Using a FQDN is very important when using BMC ProactiveNet with service models based on BMC Atrium CMDB and BMC Atrium Discovery and Dependency Mapping. All hosts must be resolvable using DNS, and resolve to the same FQDN from both BMC Atrium Discovery and Dependency Mapping and BMC PATROL.
- Identify and configure the thresholds to set at the PATROL Agent and monitoring solution level. See Threshold considerations.
- Validate that data collection and event generation are occurring on the PATROL Agent while it is still stand-alone (before connecting it to the Integration Service).
Configure and deploy the PATROL Integration Services as required
- The Integration Service must always be installed on a dedicated computer separate from the BMC ProactiveNet Server. This setup avoids unexpected performance impact of the Integration Service on the BMC ProactiveNet Server and of the BMC ProactiveNet Server on the Integration Service. This setup also allows for a more scalable architecture as the number of PATROL Agents increases.
- The Integration Service is installed via the BMC ProactiveNet Agent package installation. The BMC ProactiveNet Agent installation prompts you to enable the Integration Service, which must be enabled.
- Add PATROL Event integration support to each Integration Service node. Note that by default, the Integration Service is enabled to integrate only performance metrics from PATROL Agents. Two additional components, BMC Impact Integration for BMC PATROL and the BMC PATROL Event KM Notification Server, must be installed and configured.
Although PATROL Event integration might not be needed for all Integration Service nodes, BMC recommends configuring all the nodes consistently to support event integration. Consistent configuration simplifies administration.
- Connect a subset of the PATROL Agents to the respective Integration Services.
- PATROL Agents must be connected to the Integration Service using the automated workflow feature. Automated workflow enables the PATROL Agent to automatically initiate the connection to the Integration Service on its own (and avoids explicit management of the Integration Service component). The automated workflow feature requires setting BMC PATROL configuration variables on the PATROL Agent, which must be done using the PATROL Configuration Manager (PCM). Setting BMC PATROL configuration variables must be done only after the PATROL Agent and collection configuration for the monitoring solution has been scaled down (configured appropriately in the context of BMC ProactiveNet Server integration); otherwise, the PATROL Agents will send unnecessary data to the Integration Service).
- Starting with a subset of agents is important to avoid overloading the BMC ProactiveNet Server or Integration Service. Ideally a representation of all the monitoring solution types will be in this initial subset of PATROL Agents (because filtering at the Integration Service level might require at least one instance from the monitoring solution to be present).
- A reasonable subset of PATROL Agents must be less than 100. This would be repeated until the maximum recommended number of agents is added to the Integration Service (per the scaling guidelines).
- If two different PATROL Agents are monitoring the same target, both agents must be tied to the same Integration Service. If this is not done, the monitors from the different PATROL Agents might not be properly reconciled on the BMC ProactiveNet Server.
- Consider high availability (HA) as part of the Integration Service node deployment.
- VMware HA is a recommended option if the Integration Service is being run on a VMware VM. This option simplifies administration because it is transparent to the PATROL Agents (both the connections for the performance metrics and events automatically reconnect when the VM is restarted).
- If VMware HA is not an option, the out-of-the-box HA options can be enabled by specifying a secondary Integration Service node. There are two different configuration variable properties: one for the performance metrics connection (to the PATROL Proxy on the Integration Service node) and one for the events connection (to the Notification Server on the integration service).
See BMC ProactiveNet recommendations for high availability options and document references.
- Validate that data is being sent from the PATROL Agents to the Integration Service for both the performance metrics and events. You can do this by using the format commands in monospace which is installed with the Integration Service.
Connect the Integration Services to the BMC ProactiveNet Server
- Based on the sizing requirements, deploy and configure one or more BMC ProactiveNet Servers, if they have not already been deployed.
- Add the Integration Service nodes to the BMC ProactiveNet Server by using the Admin console. Note that Integration Service nodes are added as remote ProactiveNet Agents.
- Determine if additional filtering at the Integration Service level is required. Filtering avoids sending extra instance data and metrics to the BMC ProactiveNet Server when it is not possible to disable at the PATROL Agent and monitoring solution level. Following are common scenarios that require filtering at Integration Service level:
- Events are all that is required from an application instance (such as process up or down), but the performance metrics are not required at that granularity. In this scenario the PATROL Agent must still collect the data but the data for those respective instances does not need to be brought into the BMC ProactiveNet Server.
- Existing PATROL customers have a large amount of data being collected at each PATROL Agent (the PATROL Agents were previously configured as independent entities and not with the BMC ProactiveNet Server in mind).
- Monitoring solution application instances are very dynamic (created and deleted within the span of 1 or 2 days). These instances must not be brought into the BMC ProactiveNet Server because they will not generate a baseline pattern and will only cause overhead to the Integration Service and BMC ProactiveNet Server.
Filtering at the Integration Service level is possible by editing the PATROL Adapter instance associated with the respective Integration Service. See the [BMC ProactiveNet Data Adapter and Monitor Guide.|PN90:PDFs^ProactiveNet_Data_Adapter_and_Monitor_9.0.pdf]
Observe and confirm proper operation of the BMC ProactiveNet Server and Integration Services
- Between each batch of PATROL Agents and Integration Services deployed and configured, ensure that the BMC ProactiveNet Server and Integration Services are performing well and can still manage the load.
- Performance diagnostics for the BMC ProactiveNet Server and the respective remote ProactiveNet Agent nodes where the Integration Service is running are available in the web console. Ensure that the scalability limitations of the Integration Services are not exceeded. See BMC ProactiveNet recommendations for performance and scalability.