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.6.0-940
• SDK Manager - version 24.5.0

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.

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

ABAP Agent

SAP-350 (ASM-1191): SAP S/4 HANA 2023 Cloud Private Edition Certification

AppDynamics for SAP is now certified by SAP for S/4 HANA 2023 Cloud Private Edition - Cisco AppDynamics Monitoring for SAP® Solutions.

SAP-485 (ASM-1541): Micro Hub Support

As of release 24.8.0, OData backend correlation is supported when micro hub setting is used for backed connection. See Instrument NetWeaver Gateway

SAP-477 (ASM-1540): Custom Analytics String Length

Default string length limit was increased to 2048 characters. This limit can be adjusted using new expert parameter ANALYTICS_STRING_SIZE. See Expert Settings.

SAP-483 (ASM-1516): Default to Harmonized Schema

As of release 24.8.0, it is no longer possible to use Legacy analytics adapter for new installations. 

Upgrades from older releases will still use the Legacy analytics adapter if it was setup before the upgrade.

Legacy analytics adapter deprecation

It is highly recommended to proactively migrate away from Legacy analytics adapter as it is considered obsolete and will be deprecated in future releases. Please refer to the following guides - Migrating to Harmonized Adapter and Migrating Analytics Dashboards and Metrics.

Monitoring

Complete CrystalBridge® Monitoring 24.08 Installation and User Guide.

SAP-440 (ASM-1521): IDoc Failure Reprocessing Status

New KPIs have been created for resolved IDocs monitoring in the Collector for IDocs:

• IDOC_IN_RESOLVED_CNT: Number of resolved IDocs in inbound processing.
• IDOC_OUT_RESOLVED_CNT: Number of resolved IDocs in outbound processing.

New collector parameters ALL_STATUSES_FOR_E_IDOC_TO_DT and MAX_RETEN_IN_DAYS_FOR_ERROR_IDOC have been created for changing the default behavior of reporting data for erroneous IDocs into the detail table IDocs details. 

OOTB IDoc Monitoring dashboard was updated to contain the new metrics.

SAP-455 (ASM-1480): Custom KPI Migration

It is now possible to migrate custom KPIs from one SAP system to another. See Migrating Custom KPIs.

SAP-467 (ASM-1520): ABAP Runtime Error Monitoring Enhancements

The Collector for SAP runtime errors has been enhanced to collect additional information about short dump error analysis, information about where the dump occurred, and a description of how to correct the dump. New parameters have been created for this collector: PREFERRED_LANGUAGE and PROPAGATE_VARIABLES. See Collector for Dumps.

SAP-481 (ASM-1539): HANA Alert Monitoring Enhancements

A new field has been added for the HANA alert ID and is reported into the detail table HANA alerts. This value is automatically propagated through custom application events into HANA Alerts dashboard. See also Collector for HANA Alerts.

HTTP SDK

SAP-490 (ASM-1514) C++ SDK and OpenSSL Update

HTTP SDK now uses newest C++ SDK component, which complies with latest security standards and OpenSSL has been updated to 3.0.14.

Resolved Issues and Improvements

ABAP Agent Improvements

• ASM-1538: Business transaction snapshots are now automatically generated every time proactive SQL trace is collected.
• ASM-1547: ST05 SQL statements are now also propagated as DB calls.
• ASM-1548: Trace details are now included in log download logic.
• ASM-1559: OOTB dashboards are now uploaded using OAuth credentials.

ABAP Agent Fixes

• ASM-1155: Custom analytics schema field duplication issue has been resolved.
• ASM-1208: Corrected job runtime calculation in log download logic.
• ASM-1522: HTTP proxy settings are now correctly applied to IoT connector for SAPGUI EUM.
• ASM-1562: Automatic Web service details data collector is now limited to max 10 lines per BT snapshot.

Monitoring Improvements

• ASM-1087: Removed obsolete BWA content from scope of monitoring.
• ASM-1145, ASM-1529: Improved sort order logic for KPI groups and KPIs.
• ASM-1316: Extended monitoring log download scope.
• ASM-1457: Streamlined descriptions and order of KPIs under SAP Memory group.
• ASM-1497: Implemented option to download troubleshooting logs for Monitoring Cockpit charts. See, Adjusting the User Display Settings.
• ASM-1501: Implemented option to add standalone database monitoring via secondary connection. See, Database (generic).
• ASM-1505: Implemented improvements in file system monitoring. See, Collector for Disc/Folder Space Utilization.
• ASM-1507: Added SLT monitoring collector parameter to limit number of detail table records. See, Collector for SLT Replication.
• ASM-1523: Added disk name to disk utilization detail table. See, Collector for Disk, Memory, CPU and Network Load Monitoring.
• ASM-1527: Created troubleshooting page for "No response from async.call" errors. See, Error message "No response from asynchronous call on task "&1" in time "&2" seconds.
• ASM-1543: Adjusted database monitoring collector to monitor databases using secondary DB connection. See, Collector for Database Monitoring.

Monitoring Fixes

• ASM-1472: Implemented minor HANA backup KPI calculation adjustments.
• ASM-1500: Fixed issue in status check for passive application servers.
• ASM-1503: Records from table /DVD/MON_COLEXE are now correctly cleared when collector job is stopped.
• ASM-1531: The Collector for Background Job Monitoring now handles the custom-defined input rules for specific background job monitoring correctly. 
• ASM-1532: The Collector for User-defined SQL now creates compatible data types in the result structure for data collection according to the fields defined in the custom SQL statement.
• ASM-1533: Database-related KPIs are now also collected for SAP systems with an MSSQL database. 
• ASM-1551: It is now possible to use credentials containing special characters for SAP Web Dispatcher monitoring. 
• ASM-1554: The user documentation for CrystalBridge® Monitoring now links to the latest version in the PIM documentation (instead of the old Atlassian documentation).