Enhancements

General

Agent Dependencies

ABAP Agent components are no longer dependent on SNP Reuse Library. Reuse Library transport request was excluded from the list of dependencies and it is no longer part of the release bundle. Uninstallation transport for SNP CrystalBridge Monitoring and Reuse Library was split into two separate transports. Uninstall transport request for SNP Reuse Library can be applied when the SAP system does not contain any other SNP software that is dependent on SNP Reuse Library.

Components With Different Versions

There are AppDynamics components included in this release where version does not match with ABAP Agent components version. The following components report a version that was used in this release:

  • C++ SDK legacy - version 22.12.0-576
  • C++ SDK latest - version 24.9.1-1000

Controller connection issue in C++ SDK for Windows was resolved and newest HTTP SDK for Windows is using latest available C++ SDK 24.2.1.858.

HTTP SDK Compatibility Version

Due to C++ SDK changes in oldest supported GLIBC, ABAP Agent ships with two types of HTTP SDK:

  • HTTP SDK latest - includes newest C++ SDK version and contains all features. Requires GLIBC version 2.17 or newer (on Linux) or Microsoft Visual C++ Redistributable 2019 or newer (on Windows).
  • HTTP SDK legacy - includes a special C++ SDK version (22.12.0-576) that is compatible with older GLIBC versions. Does not support call graphs, but contains features added up to the specified C++ SDK version.


Legacy component legal statement

This Legacy HTTP SDK build ("Legacy Build") is intended to support installations on Linux systems using GLIBC versions before 2.17. You acknowledge that the Legacy Build requires the inclusion of third party libraries that are no longer supported. By using the Legacy Build, you understand and accept that such third party libraries do not receive current security patches and may contain known vulnerabilities. If you do not agree to these terms, you must not access this Legacy Build.

If the C++ libraries on supported SAP application servers cannot be upgraded, HTTP SDK can be installed on a remote Linux gateway system with sufficient GLIBC version as a workaround. See Installing HTTP SDK Manually.

Legacy component deprecation

As of release 24.11.0, Legacy Build is no longer included in the remote HTTP SDK installation scenario. It is still available for local HTTP SDK installation, but this option will be removed in near future. If your SAP system is still running on unsupported GLIBC version, it is recommended to switch from legacy local HTTP SDK scenario to latest remote HTTP SDK scenario.

Please refer to individual readme.txt files for more details.

ABAP Agent

SAP-502 (ASM-1105): BiQ Improvements

Change document class option in business process step definition will no longer require that the client code (MANDT) field is manually entered into list of custom document fields if the document table is client-dependent. Change document processing is not handling this scenario automatically.

For new installations, BiQ monitoring job will time out after 30 minutes instead of default 5 minutes. This change is also possible for existing installations using t-code /DVD/MON to modify the existing APD_BIQ monitoring job profile.

SAP-507 (ASM-1612): EUM SAP User Details

Default EUM snippet contains 3 new placeholders:

  • &USER_ID& - technical SAP user name
  • &NAME& - full name of the user
  • &EMAIL& - user e-mail address

The data will be replicated based on current User Data snapshot settings.

The placeholders can also be used in custom snippets. See Browser End-User Monitoring.

SAP-510 (ASM-1518): S/4 HANA 2023 FPS02 Compatibility

As of release 24.5.0, AppDynamics for SAP is compatible with S/4 HANA 2023 FPS02. See SAP Supported Environments.

SAP-512 (ASM-1591, ASM-1598, ASM-1610): Proactive Security Scanning

All agent components undergo advanced proactive security scans. This activity is intended to reduce response time in support tickets related to VirtualForge and similar tool scan findings.

Monitoring

SAP-424 (ASM-1575) ABAP Daemon Monitoring

This collector is used to monitor the changes and health of the running ABAP daemons available in transaction SMDAEMON. It collects the KPIs and detail table that mainly reflect the changes in the running ABAP daemons since the last run of this collector execution on the specific application server:

  • New error(s) identified in the configured ABAP daemons.
  • New event(s) identified in the configured ABAP daemons.
  • The status of the ABAP daemon has been changed.

The ABAP Daemon functionality is available as of SAP release 7.52 and higher. If the monitored SAP system does not meet this requirement, the data is not collected. See Collector for ABAP Daemon Monitoring.

A new OOTB dashboard for this monitoring area was added. See SAP General Dashboards.

SAP-479 (ASM-1577) Adjusted Authorization Concept

Existing authorization roles were adjusted and two new authorizations roles were added:

These two roles can be assigned to the designated users instead of main /DVD/MON_ADMIN role to achieve segregation of user responsibilities. Some expert functionality may still require the main /DVD/MON_ADMIN role.

All roles and their authorizations are now documented here - Overview of Authorizations Contained in Default Authorization Roles.

SAP-493 (ASM-1517) Harmonized Custom Analytics Schema for HANA DB

A new harmonized custom analytics schema 'sap_hana_data' was added. Default content was updated and some HANA-related detail tables are now replicated into this analytics schema instead of custom application events. See Mapping Between Legacy and Harmonized Analytics Schemas and Mapping Between KPIs and Metrics.

To accommodate this change, affected HANA dashboards were updated to display data in analytics widget instead of event list widget. The following dashboards were updated:

  • HANA Transactions
  • HANA SQL statements
  • HANA High availability

Affected dashboard will need to be re-uploaded. See also SAP HANA Dashboards.

SAP-504 (ASM-1363) ABAP Dispatcher Queues Monitoring

This new collector collects information about ABAP request queues for each application server. These metrics show the number of currently waiting requests in the SAP dispatcher request queue for each work process type, or they show the delta of written and read requests since the last collector execution. In addition, this collector also contains predefined alert thresholds to check if the currently waiting requests are exceeding 50% of the maximum request queue size. See Collector for ABAP Request Queue.

A new OOTB dashboard for this monitoring area was added. See SAP General Dashboards.

HTTP SDK

SAP-495 (ASM-1573) C++ SDK Update

HTTP SDK now uses newest C++ SDK component, which complies with latest security standards. This C++ SDK enables call graph root wrapper suppression.

Small stability fixes were added to SDK manager in response to OpenJDK compatibility concerns.

SAP-499  (ASM-1526, ASM-1579) Call Graph Root Wrapper Suppression

Latest HTTP SDK builds will proactively suppress call graph root wrapper logic. This will make sure that call graphs in snapshot UI will no longer show the root node with time difference between BT and the call graph. This will also suppress the Potential Issues entry. Partial call graphs will no longer indicate a false potential issue.

Resolved Issues and Improvements

ABAP Agent Improvements

  • ASM-1537: Improved deletion logic of generated SAT trace files.
  • ASM-1564: BiQ configuration is now added to downloaded logs.
  • ASM-1602: Added exception log popup to /DVD/APPD_DI_CON logic.

ABAP Agent Fixes

  • ASM-1587: Agent heartbeat job automatic clean-up logic for SM37 entries.
  • ASM-1613: Safety check "is shadow system" added to HTTP client instrumentation.

Monitoring Improvements

  • ASM-1076: Added a new troubleshooting page for the error related to no returned response for an executed asynchronous call from the central to the remote SAP system - link.
  • ASM-1152: Adjusted the logic to report the correct CPU load percentage values on the hyperthreaded CPUs according to the CPU cores instead of the logical CPUs (threads).
  • ASM-1357: It is now possible to execute required OS commands with predefined SXPG commands instead of using a CALL SYSTEM statement.
  • ASM-1394: Added new KPIs for CPU threads/logical CPUs and CPU cores on Oracle databases.
  • ASM-1395: Created automated checks for adding supported monitoring areas related to BW and IDoc monitoring into the list of supported areas of the monitored SAP system.
  • ASM-1403: Consolidated list of the default monitoring areas used for SAP system monitoring (deprecated or not added automatically by default to the list of supported areas).
  • ASM-1469: Removed deprecated authorizations for the Reuse Library and BW Analysis (Heatmap) from default CB Monitoring authorization roles.
  • ASM-1545: Adjusted the collector for database monitoring to collect metrics according to the predefined SQL statements through the secondary database connection.
  • ASM-1546: The server(s) are now pinged with the standard SXPG command with the name PING instead of the standard SAP report RSHOST14.
  • ASM-1549: Added new authorization checks to verify if all configured users (admin, RFC and BTC users) have valid CB Monitoring authorizations while adding a new SAP system.
  • ASM-1552: Created a new product class for CB Monitoring independent from the Reuse Library interface.
  • ASM-1561: Split the function to calculate the total size in the collector for disk/folder space utilization into two separate functions dedicated to calculate the total size of the specific disk or folder - link.
  • ASM-1584: Improved the logic to raise the respective SQL error details if the custom-defined SQL statement fails in lower SAP releases.
  • ASM-1586: The dummy instance of the user variant is now returned, if this instance is requested beyond the GUI context and processing.
  • ASM-1596: Downloaded monitoring logs now contain the legend for the possible values of the collector job statuses for better readability of these logs.
  • ASM-1597: Update page with KPI to metrics mapping - link.
  • ASM-1599: The last status of the collector job now reflects the current collector job status in the ALV output, if this last status no longer exists in the standard table TBTCO.
  • ASM-1607: The complete list of default KPIs in the documentation is now categorized by the respective subpages according to their predefined main system types for better readability - link.
  • ASM-1608: Added a new troubleshooting page for possible error messages while adding a new SAP Web Dispatcher system through the HTTP connection - link.
  • ASM-1611: Added reporting for the number of CPUs and the memory size for the database servers while adding a new system for an Oracle database.
  • ASM-1615: Adjusted the collector for Oracle CPU utilization to report the correct CPU idle percentage values for the hyperthreaded CPUs according to the CPU cores instead of logical CPUs (threads).

Monitoring Fixes

  • ASM-1022: The collector for Oracle memory information now loads the correct input records defined on the corresponding central SAP system.
  • ASM-1163: External servers for SAPOSCOL or SAP CCMS agents are no longer marked for monitoring by default.
  • ASM-1165: The expand and collapse function for displaying KPI groups in the KPI tree now works according to the parent group.
  • ASM-1530: The collector for number ranges now reports the correct speed values in the initial run or when a new number range record is identified.
  • ASM-1567: Correct monitoring areas for default profiles are now set to the corresponding profiles after upgrading CB Monitoring.
  • ASM-1570: The runtime error DBSQL_SQL_DEADLOCK_DETECTED is no longer raised while updating the table for the server last statuses (table /DVD/MON_SERSTAT).
  • ASM-1571: The correct ABAP data type for the string type is now initialized for the supported ABAP data types in the collector for user-defined SQL statements.
  • ASM-1574: The detail table for the monitored background jobs now uses the correct text formatting and displays the correct field descriptions.
  • ASM-1578: The report to migrate custom-defined KPIs no longer loads data if the user lacks valid authorizations.
  • ASM-1583: The obsolete ICF service INSIGHTS is no longer delivered within the standard installation transport for CB Monitoring.
  • ASM-1585: Obsolete enhancement implementations for Storage Management are no longer delivered within the standard installation transport for CB Monitoring.
  • ASM-1593: The KPI for the average of the total memory used per process on all servers now reports the correct value.
  • ASM-1594: The detail table for lock entries (SM12) now reports only long-existing lock entries that match the custom rules defined in the input table.
  • ASM-1609: The horizontal scrollbar is now displayed as expected while displaying the data for any existing detail table.
  • ASM-1623: The collector for HANA CPU utilization now calculates and reports the correct percentage values for user, system and I/O waits related metrics for CPU utilization.