SA-22494

Summary

When user clicks on "Reporting" (Management Reports) in the navigation area on the left of the Autonomic Event Services (AES) Manager Portal, it can take up to 60 seconds until the AES Reports Page displays. This time it depends on the selected cluster.

User is monitoring 11 nodes, and have more than half a million entries in the AES Developer's environment.

​Their AES alert table PEGAAM_ALERT is already hash partitioned on the CLUSTERNAME.

The display of the AES Reporting Page in the previous AES version 7.1, that customer still has in AES production environment, takes less than a second.

This behavior is only replicable for “Reports” (Reporting) in "AES Manager Portal".

Error Messages

Not Applicable.

Steps to Reproduce

Select a cluster in the AES Manager Portal and click on "Reporting" (Management Reports) in the navigation area on the left of the AES Manager Portal.

Root Cause

Root cause of problem is identified as below SQL statement. SELECT DISTINCT "PC0".pxObjClass AS "pxObjClass", "PC0".RULEAPPLICATION AS "RuleApplication"
FROM PRPC_AES_ADM.pegaam_alert "PC0"
WHERE "PC0".pxObjClass = 'PegaAES-Data-Alert'
AND (("PC0".CLUSTERNAME = 'pegadte') AND "PC0".RULEAPPLICATION IS NOT NULL AND
("PC0".RULEAPPLICATION <> 'NA') AND ("PC0".RULEAPPLICATION <> 'null'));

Resolution

Perform the following local-change:

1. Apply defer load on dynamic layout "AnalyzeApplicationPerformanceForAlerts"in "AESReportsContainer" section as their is a drop-down which fetches the name of all the monitored application querying PEGAAM_ALERT table. When the above mentioned dynamic layout is deferred loaded as in later release (AES 7.2) the problem gets resolved.

2. Also, create a combined index on "ClusterName, pxObjClass, RuleApplication" columns of PEGAAM_ALERT tunes the SQL query and enhances the performances as well.

A feedback request(FDBK-15104) was raised to have an alternative implementation for fetching the name of application monitored which needs to be loaded in one of the drop-down in "AnalyzeApplicationPerformanceForAlerts" section.