• Spaces
  • Collections
  • Help
    • ×
     
     
    •  
    BMC PATROL for Amazon Web Services 2.0

    Page tree

    Unsupported product

     

    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.

    The scalability material in this section might vary according to your specific environment.
    The information described in this section is only tested for the Amazon Elastic Compute Cloud (EC2), Amazon Elastic Block Store (EBS), Amazon Elastic Load Balancing (ELB), and Amazon Relational Database Services (RDS) web services.

    PATROL for Amazon Web Services has been tested to scale using 10 accounts, each having 20 Amazon EC2 instances, with:

    • Approximately 324 parameters per account
    • 16 parameters per EC2 instance
    • Approximately 3240 parameters in total
    • Collection interval for Inventory data set to 1 minute
    • Collection interval for EC2 performance data set to 3 minutes 
    • Collection interval for ELB/EBS performance data set to 5 minutes

    BMC recommends that you set the Java Heap settings by using the /AWS/javaOpts variable as follows:

    • Initial heap size for Java Collector Process = 256 Megabytes
    • Max heap size for Java Collector Process = 300 Megabytes
      For more information about changing the Java heap settings, see PATROL Agent configuration variables.

    Scalability is directly proportional to the number of Amazon EC2 instances, as any increase in the number of Amazon EC2 instances is proportional to an increase in the number of requests sent to Amazon Web Services. Increasing the number of Amazon EC2 instances or accounts (with the default collection interval) could result in missing data points for several parameters. If Amazon Web Services is flooded with requests, it might display a Rate exceeded error message or throttling-related error messages. The following factors affect throttling in Amazon Web Services:

    • Throttle limits are not based on the IP address of the computer that submitted the request. Instead, they are based on customer account, API, region, and (in some cases) availability zone.
    • Exceeding a certain rate of Gets per minute or higher "burst" rate per second.

    Write a comment...
    © Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.