Sizing charts and guidelines for event and impact management

This topic presents recommendations and considerations for different size Infrastructure Management environments that include event management and impact management. Examine the guidelines for each environment to determine which size fits your requirements. The values provided represent the maximum values recommended for the tested parameter.

The following tables provide sizing summaries for an environment that incorporates both event and impact management in small, medium, and large environments:

Sizing chart for Infrastructure Management Consoles

Characteristic	Small environment	Medium environment	Large environment
Concurrent number of users—operator console	25	50	100
Concurrent number of users—administration console	1	1	1

Sizing chart for impact management

Information about a CI can be stored in Infrastructure Management without the BMC Atrium CMDB. However, this information will be limited to performance and event management. BMC Atrium CMDB is required from an asset management or configuration management perspective. For more information, see How the Common Data Model represents service models Open link .

Characteristic	Small environment	Medium environment	Large environment
Number of CIs in CMDB	100 K	100 K	100 K
Number of services in CMDB	15	25	50
Number of CIs in the Infrastructure Management Server	15 K	25 K	50 K
Number of CIs per cell	15 K	25 K	50 K
Maximum number of CIs per service model	5 K	10 K	20 K
Number of services in BMC TrueSight Infrastructure Management Server	15	25	50
Service model depth	5 levels	6 levels	6 levels

Sizing chart for event management

Characteristic	Small environment	Medium environment	Large environment
Number of intelligent events per day	0	0	0
Number of external events per day	100 K	200 K	400 K
Number of remote cells	0	5	10

Sizing chart for memory configuration (MaxHeap metrics)

Characteristic	Small environment	Medium environment	Large environment
Size of Jserver MaxHeap	2 GB	4 GB	8 GB
Size of rate MaxHeap	default	default	default
Size of agent controller MaxHeap	default	default	default
Size of Self-Monitoring Service MaxHeap	default	default	default
Size of Integration Service MaxHeap	N/A	N/A	N/A

Small environment guidelines

Consider the following guidelines when planning a small event and impact management environment:

You can host the server adapters and event adapters on the same host.
Distribute event correlation, deduplication, and normalization to a Remote Cell, which sends this data to the BMC TrueSight Infrastructure Management Server.

Small deployment, event and impact management

Medium environment guidelines

Consider the following guidelines when planning a medium event and impact management environment:

Publish up to 10,000 configuration items at one time. For information about publishing, see Managing the Publishing Server .
Configure the BMC Event Adapters on the BMC TrueSight Infrastructure Management Servers to send events. For details, see Configuring BMC Event Adapters to start collecting events.
Distribute event correlation, deduplication, and normalization to one or more Remote Cells, which send this data to the Infrastructure Management Server.

Medium deployment, event and impact management

Large environment guidelines

Consider the following guidelines when planning a large event and impact management environment:

Publish up to 20,000 configuration items at one time.
Install BMC Atrium CMDB on different computers. For hardware requirements, see the BMC Atrium Core documentation .
Install Infrastructure Management Remote Cells at each remote location. These Remote Cells collect events directly from the event sources, filter sympathetic events, and apply normalization and deduplication rules to other events. Only important events are propagated to the Infrastructure Management Server.
Each remote location runs the Remote Cell as well as adapters and integration components. This requires a dedicated computer that meets resource requirements.

If you exceed the capacity for a large environment, additional Infrastructure Management Server can be added. See Distributed service model Open link .