Health Dashboard - Views - Performance issue

When connecting to the HD dashboard, there is some delay (some minutes) before the information is displayed. This troubleshooting describes the different steps to follow in order to identify/explain the root cause of performance issue on ADD response time.

When connecting to the HD dashboard, there is some delay (some minutes) before the information is displayed.

1. Check if your configuration follows the requirements
2. Relevant input
3. If the issue is at the login phase and you are using LDAP to connect to the HD portal, check whether the issue is due to LDAP server performance issue
4. Check whether log are activated, as this may lead performance issue
5. Check whether issue is on the network (connection between the tomcat application and the postgres server)
6. Check whether issue is on the postgres database.
7. If your case does not fall under any of the cases above, please contact CAST Support with Relevant Input.
   For CAST Technical Support only. Please refer to the page - Health Dashboard - Information - How to reproduce HD issues

Check if your configuration follows the requirements

Case 1: If you have greater than 200 applications

Based on discussions with Product Management Team on this issue, HD currently only supports up to 200 applications.  Therefore, trying to run HD beyond this point is outside the scope of support and would need to be addressed via a feature request for future versions.

Please make sure you size your environment based on current CAST guidelines as per the documentation for the release.  For 7.3.X, those are available here:

The product management team has suggested a user could possibly slice and dice their applications with a particular focus within HD that might allow this to work within the current product guidelines.  For example, if some subset of applications (<200) were more focused on performance, put those in one HD dashboard with the corresponding tiles.  If another subset were more focused on security, then put those in another HD with the corresponding tiles.

Please go to the community section to raise a Feature Request in the helpdesk system if you are outside the scope of support in this case.

If the issue is at the login phase and you are using LDAP to connect to the HD portal, check whether the issue is due to LDAP server performance issue 

If you are using LDAP to connect to the HD portal, slowness in the reponse time of the HD portal may be due to performance issue of the LDAP server. To check this, please proceed as following:

1. If you have HAR trace, you can use the viewer of HAR files with chrome: http://ericduran.github.io/chromeHAR/
2. if you do not have HAR trace, you need to connect to HD on chrome, click on F12, reproduce the issue, you will get HAR trace at the bottom of the page

In the HAR trace look for:

   rest/

     login

This is the login time for LDAP. If the elapsed time for this step is the most representative one in the whole response time, then issue is on the connection to the LDAP server. You need to contact your network administateur as issue not related with CAST product 

For example:

The login time to the HD portal is less than 6 seconds and you observe that the "rest/ login" time stands for 5 seconds, then issue is on the LDAP server

Check whether log are activated

To be done. Contact support  

Check whether issue is on the network (connection between the tomcat application and the postgres server)

You can check whether issue is due to network performance issue between the server hosting the tomcat application and the postgres server. For this you can run the following ping test from your tomcat application server:

1. Open a command line (cmd) from the server hosting the tomcat application
2. Run the following command: ping <postgres-server>

If the response time is the most representative one in the whole HD response time, issue is on the network. Please contact your network administrator

Check whether issue is on the postgres database

 You can check whether issue is due performance issue on postgres database. For this, you can check for query exection time on your HD schema.

 Run the following query 2 times: (1 time is the max time, 2nd time is the min time)

select r.OBJECT_ID, r.SNAPSHOT_ID, r.METRIC_ID, r.METRIC_NUM_VALUE, r.METRIC_VALUE_INDEX
from DSS_METRIC_RESULTS r
where
 r.METRIC_VALUE_INDEX in (0,1,2) and r.OBJECT_ID in (select 
distinct(application_id) from adg_delta_snapshots) and r.METRIC_ID in 
(60017)   and r.SNAPSHOT_ID in (select distinct(last_snapshot_id) from 
adg_delta_snapshots)

If the execution time of the query is the most representative one in the whole HD response time, issue is on the postgres schema. Please contact CAST support, providing with the required input, the query and the execution time of the query

Reference webcall 29858