The Solution Diagnostics are a tool within the Administrator Workcenter of your SAP Hybris Cloud for Customer solution, which you can leverage to identify potential issues in performance and stability in your tenant.
When opening the Solution Diagnostics, it will by default display all issues available. By using the advanced filter in the list, you can filter for specific categories, types of issues and priority.
A regular check of this tool is recommended, as the reports that populate this list of issues are running weekly.
The result list shows the selected potential issues, which were automatically identified by the system through different mechanisms. Be aware that not all items in the list might necessarily point to definite problems, but each entry requires a manual investigation, based on the type and recommendation of the problem. The five different types are detailed as followed:
1. ABSL Code
Issues of check type “ABSL Code” are pointing towards potential problems within custom code (PDI). Each row starts with the respective path and file that contains the potential issue. The issue description can be distributed over several lines in the list. Hence, read the information from top to bottom:
In this example, the first row is the “header”, indicating the start of the check for “Possible Dumps due to missing IsSet() Checks”. After that, the list of identified issues follows, with two rows per entry. The first row indicates the type of error, e.g. “Avoid dump : Use IsSet() to check the value returned by association CurrentCommon”, while the second row provides more information about the exact location in the file, where the issue can be found.
As a further help to identify and fix the problem, you can run the Performance Check for the file in question within the Sap Cloud Applications Studio. For that, just right-click the .absl file within the Solution Explorer and select “Run Performance Check”. The same errors/warning, as visible within the Solution Diagnostics, should now appear within the Error List of the SAP Cloud Applications Studio.
For more information about Performance Best Practices within the SAP Cloud Applications Studio, see the following Blog entry: https://blogs.sap.com/2015/08/27/sap-cloud-application-studio-performance-best-practices/
2. Cold Interactions
Cold interactions (e.g. the message “High number of cold interactions observed with 30% of total interactions”) indicate that an unusual high number of user interactions were carried out in a “cold” state. This means that browser or server caches had to be filled during the request, leading to increased response times for the interaction. For more details about cold requests and how to analyze them in your tenant, see the part “#1 Browser Cache Clearing” in the following article:
Or refer directly to the following blog entries:
3. Data Scope Activation
Issues of this type indicate that for the specified custom UI components, Data Scope Handling is not activated. However, it is recommended to enable this feature in most cases, as it might Improve Response Times when opening these UI components, due to the reduced amount of data required to be fetched in the call. For more information, see the following article: https://blogs.sap.com/2016/09/26/ui-designer-data-scope-activation/
4. Event Clubbing
Issues of this type indicate that for the specified custom UI components, the event (or operation) clubbing is not enabled. However, it is recommended to enable this feature in most cases, as it might improve response times, especially on slow connections with a high latency. For more information see the entry “Enable operation clubbing” in the following article: https://blogs.sap.com/2015/08/27/sap-cloud-application-studio-performance-best-practices/
5. SDK Exception
Issues of this type point to Runtime Errors (“shortdumps”) that were caused by custom code (PDI).