Page tree

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.

Skip to end of metadata
Go to start of metadata

This topic presents recommendations and considerations for different size BMC ProactiveNet environments that include data collection and event management. Examine the guidelines for each environment to determine which size fits your requirements.

Using hardware configured for a small environment

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

  • In a small environment, you can collect and analyze up to 15,000 monitor instances and up to 250,000 attributes.
    Use one BMC ProactiveNet Server and one 64-bit BMC ProactiveNet Integration Service as the data collectors. One 64-bit Integration Service can handle up to 7,500 monitor instances and 125,000 attributes.

    Note

    The BMC ProactiveNet Integration Service on Solaris, whether 32-bit or 64-bit computer, cannot monitor more than 125,000 attributes.

  • Install the BMC ProactiveNet Server and BMC Event Adapters on the same host, but you must install the Integration Service on a separate computer.
  • Distribute event correlation, deduplication, and normalization on BMC ProactiveNet Remote Cells.
  • Up to 25 concurrent users can be simultaneously logged in and accessing the BMC ProactiveNet Server.
  • (Sybase only) To improve I/O throughput, use separate disks for the operating system on which BMC ProactiveNet Server is deployed, and the database. Ensure that each disk has its own disk controllers.

Using hardware configured for a medium environment

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

  • In a medium environment, you can collect and analyze up to 50,000 monitor instances and up to 500,000 attributes.
    Use one BMC ProactiveNet Server and at least two 64-bit BMC ProactiveNet Integration Services as the data collectors. One 64-bit Integration Service can handle up to 25,000 monitor instances and 250,000 attributes.

    Note

    The BMC ProactiveNet Integration Service on Solaris, whether 32-bit or 64-bit computer, cannot monitor more than 125,000 attributes.

  • Distribute data collection on Integration Services so that the server is dedicated to the primary server processes (analytical engine, object cache, and agent controller). The Self-Monitoring Service, which is automatically installed on the BMC ProactiveNet Server, collects metrics about only BMC ProactiveNet Server performance.
  • If you expect the total number of attributes for the environment to grow beyond 500,000 attributes, use a large-environment deployment so that the system can accommodate growth smoothly.
  • You can deploy the Integration Service on a VM that meets the resource requirements.
  • Configure the BMC Event Adapters on the BMC ProactiveNet Servers to send events. For details, see BMC ProactiveNet Installation and Configuration Guide and BMC Event Adapters User Guide.
  • BMC ProactiveNet Cells perform event correlation, deduplication, and normalization, and send this data to the BMC ProactiveNet Server.

Using hardware configured for a large environment

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

  • In a large environment, you can collect and analyze up to 120,000 monitor instances and up to 1,200 K attributes.
    Use one BMC ProactiveNet Server and five 64-bit BMC ProactiveNet Integration Services as the data collectors. One 64-bit Integration Service can handle up to 50,000 monitor instances and 500,000 attributes.

    The total number of Integration Services that has to be configured for a large environment can vary from 3 to 5 in number. Ideally, three Integration Services will be sufficient  for large environments. There is no limitation on the number of Integration Services used, if you have no more than 50 K instances on one integration service and no more than 120 K instances on all integration services. 

     

    Note

    The BMC ProactiveNet Integration Service on Solaris, whether 32-bit or 64-bit computer, cannot monitor more than 125,000 attributes.

  • Distribute data collection on Integration Services so that the server is dedicated to the primary server processes (analytical engine, object cache, and agent controller). The Self-Monitoring Service, which is automatically installed on the BMC ProactiveNet Server, collects metrics about only BMC ProactiveNet Server performance.
  • For optimum performance, minimize the number of monitors running on the BMC ProactiveNet Server's Self-Monitoring Service.
  • Configure each BMC ProactiveNet Server so that it contains an entire line of business, instead of spreading the monitoring across servers.
  • You can deploy the Integration Service on a VM that meets the resource requirements.
  • Install a BMC ProactiveNet Remote Cell in 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 event manager of the BMC ProactiveNet Server.
  • Each remote location runs a BMC ProactiveNet Remote Cell instance, adapters, and integration components. Each remote location requires one dedicated computer, scaled according to the Integration Service scaling recommendations.