For event and impact reporting, BMC ProactiveNet propagates events and component status changes from BMC ProactiveNet Servers to BMC ProactiveNet Report Engine. For performance reporting, BMC ProactiveNet propagates performance data and its supported configurations from a single instance of a BMC ProactiveNet Server to a single instance of a BMC ProactiveNet Report Engine.
In BMC ProactiveNet Performance Management Reporting version 9.0, you can continue to gather event data from multiple BMC ProactiveNet Server Cells into a single BMC ProactiveNet Report Engine, irrespective of whether all the cells are pointing to the same BMC ProactiveNet Server or different BMC ProactiveNet Servers. However, for performance reporting, a separate instance of the Report Engine is required for each BMC ProactiveNet Server. Multiple BMC ProactiveNet Servers cannot use a single Report Engine instance.
BMC ProactiveNet Report Engine then aggregates and summarizes the data and stores the processed data in the Oracle database. The impact reports are supplemented with associated service information and the performance reports are supplemented with associated BMC ProactiveNet Server configuration information.
The following figure depicts the architecture of BMC ProactiveNet Performance Management Reporting.
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks
2 Comments
William Bannister
The architecture view above is incomplete. If needs to show three ProactiveNet servers in both views. There also needs to be a composite view with 3 ProactiveNet servers provide both events and data. Any architecture scaling limits should be listed here as well.
Michael Ashall