Sizing the Presentation Server for Infrastructure Management data collection
This topic provides sizing summaries for TrueSight Infrastructure Management environments that incorporate data collection for the TrueSight Presentation Server.
It is important to estimate the size of your deployment correctly because the steps you follow and the design elements vary depending on the size of the deployment. Use the following sizing and scaling recommendations to prevent oversizing or undersizing your deployment.
The values provided represent the maximum values recommended for each environment type. The number of components connected to the TrueSight Presentation Server can vary depending on the deployment type and do not affect these values.
Sizing chart for data collection by one TrueSight Presentation Server
Number of devices
Number of events per day1
Number of groups2
|Number of applications||1,500|
|Number of services||3,000|
|Number of concurrent users||10|
|Number of PATROL Agent Access Control Lists (ACLs)||200||1,000||1,000|
|Number of roles||50||250||250|
|Number of user groups||75||300||300|
|Number of authorization profiles||75||150||150|
|Number of App Visibility Manager (APM) agents||500||1,000||1,500|
|Number of enabled Infrastructure policies||100||1,000|
*For 11.3.02 and later only, not supported on 11.3.01.
+For 11.3.03 only. Requires the following additional configuration:
- Edit the installedDirectory\truesightpserver\modules\tomcat\conf\server.xml file and update the following property:
<Connector connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="2048" port="80" protocol="HTTP/1.1" redirectPort="443"/>
<Connector connectionTimeout="20000" maxThreads="500" acceptCount="50" enableLookups="false" maxHttpHeaderSize="2048" port="80" protocol="HTTP/1.1" redirectPort="443"/>
- Edit the installedDirectory\truesightpserver\conf\secure\dbvault.ks file and add the following property at the end of the file:
#Wed Dec 04 11:14:37 IST 2019
1. The total number of events per day that a TrueSight Presentation Server can handle includes intelligent events, external events, and TrueSight App Visibility Manager server events.
2. The test environment had only one group with 50,000 monitor instances and all other groups had an average of 100 monitor instances only. Groups consisted of both auto-sync and manual groups.
Sizing details for KM deployment and PATROL Agent upgrades
The maximum number of PATROL Agents supported at a time for deploying packages and upgrading PATROL Agents is 500.
Sizing details for rule-based groups (applicable only to version 11.3.03 and later)
The following table summaries the sizing details for rule-based groups that are created using Meta Tags and short-term instances groups. The tests are conducted on a large deployment environment.
|Parameter||Rule-based groups||Short-term instances group|
|Number of groups per nesting level||3000||1|
|Total number of groups||12000*||1|
|Number of instances per child group||200||NA|
|Total number of instances||120000**||34000|
|Number of devices per group||4||5|
|Total number of devices||120000||5|
*Total groups = 3000 (level 0 groups) + 3000 (level 1 groups) + 6000 (level 2 - child groups = 3000 + 3000)
|**Total instances = 200 * 6000 (number of instances per child group * total number of child groups)|