Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

BMC ProactiveNet Performance Management sizing and scalability


The sizing for BMC ProactiveNet Performance Management (BMC ProactiveNet) depends on performance data and monitored events. The following topics explain the sizing for BMC ProactiveNet:

Estimating performance data or the number of attributes

To size your environment correctly, you must complete the following procedures in the order as listed:

  1. Determine the types of monitors that are required to monitor your environment. This is determined by the types of devices that you want to monitor in your environment.
    1. Estimate the total number of monitored instances for each monitor type.
    2. Calculate the total number of attributes to be monitored based on the monitor type and the number of monitor instances per monitor type.
  2. Consider the effect of polling periods on the number of attributes. The BMC ProactiveNet Performance and Scalability Guidelines specifies the number of attributes based on 5-minute polling. If polling is faster, the effective number of attributes will be higher by a factor of 2.5.

In a hybrid environment, resources are shared between the data collection and event management functions. Therefore, a hybrid environment handles fewer attributes than a dedicated data collection environment and fewer events than a dedicated event management environment.

BMC ProactiveNet Server resource requirements

Environment

Devices

Attributes

Events per day

Virtual CPU

Memory

Hard drive

Small

2000

50K or fewer

2K or fewer

2

8 GB

100 GB

Medium

10000

300K

10K or fewer

8

24 GB

300 GB

Large

20000

600K

20K or fewer

2 servers of 8 each

2 servers of 24 GB each

2 servers of 300 GB each

BMC ProactiveNet Agent resource requirements

The following table lists the sizing constraints for a BMC ProactiveNet Agent that acts as a consolidator to import data from BMC PATROL Agents using Integration Service and the BMC Transaction Management Application Response Time server.

Import from

Attributes

Virtual CPU

Memory

BMC PATROL

125K

2

2 GB

BMC Transaction Management Application Response Time

45K

2

2 GB

BMC PATROL

600K

4

8 GB

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Cloud Lifecycle Management 3.0