Sizing App Visibility and Synthetic TEA Agent components
Consider the following sizing and scalability guidelines when planning your BMC TrueSight App Visibility Manager deployment. These guidelines also apply to deployment of BMC Synthetic Transaction Execution Adapter (TEA) Agents.
App Visibility collector database sizing
The App Visibility collector database must be scaled to your environment. To calculate the maximum database size, use the following equation:
The default maximum database size is 100 GB, which is enough for 10 agents in the aforementioned environment. For information about changing the App Visibility collector database settings, see Changing-App-Visibility-collector-settings.
Maximum number of components per deployment
Apply the following guidelines to your deployment, per tenant:
- Maximum number of App Visibility agents or synthetic TEA Agents per App Visibility collector = 100
- Maximum number of App Visibility collectors per App Visibility portal = 5
- Maximum number of App Visibility agents or synthetic TEA Agents per App Visibility portal = 500 (divided among 5 App Visibility collectors)
- Maximum number of App Visibility portals per Presentation Server = 1
App Visibility collector sizing
To install the App Visibility collector software and database, the computer must have approximately 2 GB of free disk space.
If all components are installed together, approximately 2.1 GB of disk space is required.
App Visibility portal sizing
Disk space requirements for the App Visibility portal software and database are the same, no matter how many App Visibility collectors are used.
To install the App Visibility portal software and database, the computer must have approximately 2 GB of free disk space.
If all components are installed together, approximately 2.1 GB of disk space is required.
App Visibility proxy sizing
To install the App Visibility proxy software, the computer must have approximately 400 MB of free disk space.
If all components are installed together, approximately 2.1 GB of disk space is required.
Only one App Visibility portal can be configured with the Presentation Server. For deployment guidance, see also Operations Management basic deployment with App Visibility Manager and Operations Management service provider and tenant deployment.
Synthetic TEA Agent sizing
A single synthetic TEA Agent can process up to 120 Execution Plans when the Execution Plan references a single web-based script. This limit is set by the system.
If your scripts produce a high volume of user-interface transactions, such as browser-driven scripts, BMC recommends that you limit the TEA Agent to 50 scripts.
There is no limit to the number of TEA Agents that you can install on a single computer.
For information about Execution plans, see Editing-an-application-s-synthetic-settings.
Hardware sizing for deployments
Based upon the calculated size of your deployment, select the appropriate equipment for optimum performance.
App Visibility server resources for different deployment sizes—without synthetic transactions
* Divide the required disk size by the number of collectors: <diskSize> / <numberOfCollectors>
App Visibility server resources for different deployment sizes—with synthetic transactions
Calculations are for transactions with ten custom timers or page timers per transaction. For transactions that don't use timers, database size requirements may be smaller.
Database size calculations assume a retention period of 35 days.
Related topics
System requirements for App Visibility
Preparing-for-the-App-Visibility-server-installation
Configuring-App-Visibility-after-installation
BMC-TrueSight-Operations-Management-basic-deployment