Enhancements

General

Components Without Updates

There are components included in this release that were not updated. The following components report a version where they were last changed:

  • SDK Manager - version 22.8.0

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 23.11.1-753
  • C++ SDK for Windows - version 23.8.0.639
HTTP SDK 24.2.0 for Windows uses an older C++ SDK 23.8.0.639 version due to a bug in C++ SDK 23.11.0 version. 

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-369 (ASM-1381): Metric Batch Reporting

ABAP Agent and HTTP SDK components were extended to allow batch reporting of metrics. Older releases needed to carry out individual calls from ABAP Agent to HTTP SDK to register and report each metric value. This functionality will reduce the number of calls from ABAP Agent to HTTP SDK and reduce the agent footprint.

This feature will work automatically from ABAP Agent version 24.2.0 and HTTP SDK version 24.2.0. If older HTTP SDK version is used in combination with newest ABAP Agent version, ABAP Agent will automatically fall back to old metric reporting mechanism.

New expert setting 'HTTP_SDK_METRIC_BATCH' can be used to suppress this functionality and report metrics one by one. See Expert Settings.

SAP-416 (ASM-1379): S/4 HANA 2023 Compatibility

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

SAP-418 (ASM-1386): Exit Calls Into Primary SAP Database

ABAP Agent can now generate exit calls into primary SAP system database.

These exit calls are not intended to show real interactions with the SAP database, but to add option to correlate SAP Business Transaction snapshots with Database agents for supported database types. This means that the database call counters and execution times for these exit calls won't be accurate, but a business transaction snapshot will contain additional details if the primary SAP system database is instrumented with Database agent.

This feature is off by default. It can be turned on via new expert setting 'BT_DATABASE_EXITCALL'. See Expert Settings.

SAP-420 (ASM-1389): Call Graph root.root Handling

Call graphs generated for HTTP-like SAP Business Transactions (Generic HTTP, BSP, OData, WebServices, etc.) could be affected by an issue where a significant part of the call graph time existed in the root node.

Root cause of this issue is the fact that standard SAP ABAP tracing logic used to collect the call graph data does not include trace-induced overhead into the recorded statement execution times. This is intended to provide an approximation of the traced session to look as if the trace was not active. A side effect of this is that the recorded statement execution times don't correspond with real statement execution times that are bigger due to the trace overhead. The sum of trace overheads for each recorded statement is the time that propagates to the root node of the call graph because the total call graph time is smaller than the business transaction runtime.

As of this release, both call graph parsers now contain logic that distributes the unaccounted for ABAP trace overhead across all recorded statements before the call graph is constructed. This will effectively undo the standard SAP ABAP trace behavior and add the trace-induced overhead back into all recorded statement execution times.

Monitoring

See SNP CrystalBridge® Monitoring Release 24.02.

SAP-347 (ASM-968, ASM-1088, ASM-1374, ASM-1377, ASM-1397): Removing ReuseLibrary Dependencies

Most of ReuseLibrary dependencies are now removed. This is an ongoing effort to reduce the agent footprint and make installation of future versions easier and faster. Many Code Inspector findings were resolved in this process. The goal is to start shipping ABAP Agent without the ReuseLibrary component in one of the upcoming versions.

SAP-430 (ASM-1416): Collect External ID via Application Log Monitoring

Application log collector will now collect 'External ID' field from SAP application logs (t-code SLG1). This value will be propagated to the Controller or Event Service with existing custom application events or custom analytics data based on Monitoring Connector Mapping. See also Collector for Application Logs.

Resolved Issues and Improvements

ABAP Agent Improvements

  • ASM-1368: Adjusted usage of CL_HTTP_UTILITY logic to fix compatibility issues with older SAP releases.
  • ASM-1426: Added expert parameter to suppress Certificate Revocation List checks (Windows only). See Expert Settings.

Monitoring Improvements

  • ASM-790: Added new delay and runtime statistics KPIs for scheduled background jobs - link.
  • ASM-1083: Added new KPI for longest running job - link.
  • ASM-1282: Removed "Input table '/DVD/MON_RFC_I1' doesn't provide any valid record” warning message in case RFC connection monitoring is not used.
  • ASM-1299: Possibility to use comments to omit already defined SQL statements in the Collector for User-defined SQL.
  • ASM-1303: Added logic in XPRA report to delete already deprecated configuration properties.
  • ASM-1330, ASM-1361: Work process monitoring improvements - link.
  • ASM-1346: Update request monitoring improvements - link.
  • ASM-1362: Added new alerting thresholds and updated descriptions for ICM-related KPIs.
  • ASM-1366: Added option to download logs from Monitoring Cockpit.
  • ASM-1372: Compatibility adjustments for HANA Thread info monitoring on HANA SPS7.
  • ASM-1392: Updated short descriptions for Oracle Session-related KPIs.
  • ASM-1393: New alerting thresholds added for CPU load KPIs.
  • ASM-1398: Consolidation of KPI units for seconds to one common format "sec".
  • ASM-1399: Option to exclude already started jobs from delayed job calculation - link.
  • ASM-1400: Compatibility adjustments for free physical memory calculation metric on SAP_BASIS 756 and newer.
  • ASM-1415: BOBJ monitoring documentation was updated - link.
  • ASM-1420: SQL injection checks added to DB size calculation functions.

Monitoring Fixes

  • ASM-1268: Wrong column names defined for detail table “aRFC resource errors”.
  • ASM-1341: Fixed issue where functionality to stop monitoring for the selected system did not stop all scheduled collector jobs.
  • ASM-1342: Fixed issue where system metrics-related KPIs for Oracle database monitoring were not collected due to the missing “ORACLENODE” external server type.
  • ASM-1355: Fixed issue in the KPI creation wizard if any database function was used for modifying the date/time-related placeholder values.
  • ASM-1359: Fixed F4 help issue when selecting HANA / Oracle DB connection.
  • ASM-1367: Fixed message counter issue when switching from aggregated to non-aggregated view.
  • ASM-1376: Resolved codepage conversion issue when extracting details from RFC queues.
  • ASM-1391: Fixed issue caused by conflict of various data types while handling KPI value overflow.
  • ASM-1401: Correction in HANA Log buffer wait percentage calculation.

JCo Extension Fixes

  • ASM-1430: Adjusted WebService backend naming logic to avoid exposing connection authentication details.