Sizing charts and guidelines for event and impact management
Sizing chart for TrueSight Infrastructure Management Cell processing event rate
Sizing chart for Infrastructure Management Consoles
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.
Sizing chart for event management
Sizing chart for memory configuration (MaxHeap metrics)
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.