The TrueSight console might not be displayed because of one of the following reasons:
- Load balancer name not configured - If you have installed the TrueSight Presentation Server in High Availability and the load balancer is not configured, the TrueSight console is not displayed if you access the TrueSight console with the load balancer.
Solution
Use the following commands to configure the load balancer name:tssh properties set loadbalancername <loadbalancername>
tssh properties reload
- Changed load balancer name - If you change the load balancer name after starting the TrueSight Presentation Server, and then if you try to connect to the TrueSight Presentation Server with the changed load balancer name, the TrueSight console might not be displayed.
Solution
Use the following commands to configure the load balancer name:tssh properties set tspsProxyHosts
alias1,alias2,proxy1,proxy2,changedloadbalancername
tssh properties reload
- Cross-Site Request Forgery (CSRF) validation - The TrueSight Presentation Server validates all incoming requests to prevent CSRF attacks. If you are connecting to the TrueSight Presentation Server with an alias or a proxy name, the TrueSight console might not be displayed.
Solution
Use the following commands to configure all hosts, aliases, or proxies for CSRF validation:
tssh properties set tspsProxyHosts
alias1,alias2,proxy1,proxy2,loadbalancername
tssh properties reload
If you face a UI performance issue in the TrueSight console because of CSRF validation, and if you wish to disable the filter, click here to know more about disabling the filter. However, BMC recommends that you do not disable the CSRF filter.