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

Parameter	POC or Demo	Medium	Large
Number of devices	12,000	60,000	120,000
Number of events per day¹	200,000	900,000	1,500,000
Number of groups²	3,000	6,000	10,000
Number of applications			1,500
Number of services			3,000
Attributes	650,000	5,000,000	8,500,000
Monitored Instances	100,000	750,000	1,250,000
Number of concurrent users	10	60	300⁺
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	20,000

⁺Requires the following additional configuration:

Click here to expand...

Edit the installedDirectory\truesightpserver\modules\tomcat\conf\server.xml file and update the following property:
<Connector SSLEnabled="true" ciphers="TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_DSS_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_SHA256,TLS_ECDHE_RSA_WITH_AES_128_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_SHA,TLS_ECDHE_RSA_WITH_AES_256_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_SHA384,TLS_ECDHE_RSA_WITH_AES_256_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_SHA,TLS_DHE_RSA_WITH_AES_128_SHA256,TLS_DHE_RSA_WITH_AES_128_SHA,TLS_DHE_DSS_WITH_AES_128_SHA256,TLS_DHE_RSA_WITH_AES_256_SHA256,TLS_DHE_DSS_WITH_AES_256_SHA,TLS_DHE_RSA_WITH_AES_256_SHA" clientAuth="false" compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/javascript,application/json,application/json" compression="on" compressionMinSize="1024" keystoreFile="/data1/TrueSight/truesightpserver/conf/secure/loginvault.ks" keystorePass="changeit" maxThreads="300" port="8043" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslProtocol="TLSv1.2" useServerCipherSuitesOrder="true"/>
to
<Connector SSLEnabled="true" ciphers="TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_DSS_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_SHA256,TLS_ECDHE_RSA_WITH_AES_128_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_SHA,TLS_ECDHE_RSA_WITH_AES_256_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_SHA384,TLS_ECDHE_RSA_WITH_AES_256_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_SHA,TLS_DHE_RSA_WITH_AES_128_SHA256,TLS_DHE_RSA_WITH_AES_128_SHA,TLS_DHE_DSS_WITH_AES_128_SHA256,TLS_DHE_RSA_WITH_AES_256_SHA256,TLS_DHE_DSS_WITH_AES_256_SHA,TLS_DHE_RSA_WITH_AES_256_SHA" clientAuth="false" compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/javascript,application/json,application/json" compression="on" compressionMinSize="1024" keystoreFile="/data1/TrueSight/truesightpserver/conf/secure/loginvault.ks" keystorePass="changeit" maxThreads="500" acceptCount="50" port="8043" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslProtocol="TLSv1.2" useServerCipherSuitesOrder="true"/>
Edit the installedDirectory\truesightpserver\conf\secure\dbvault.ks file and add the following property at the end of the file:
hibernate.c3p0.max_size=300
For example:
#Wed Dec 04 11:14:37 IST 2019
secret=<value>
identity=administrator
port=5432
host=localhost
hibernate.c3p0.max_size=300

^{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.}

Note

For information about the TrueSight Infrastructure Management sizing and scalability considerations, see Sizing and scalability considerations for Infrastructure Management.

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

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
Nesting levels	2	0
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)

Sizing the Presentation Server for Infrastructure Management data collection

Sizing chart for data collection by one TrueSight Presentation Server

Sizing details for KM deployment and PATROL Agent upgrades

Sizing details for rule-based groups

Comments