ABAP Agent components are now migrated to calendar versioning as of this release.
Automatic RFC Destination Blacklisting (ASM-319, added in version 4.5.1911.0) can now be adjusted. See Configure RFC Settings - RFC Blacklist.
The terminal ID value is now excluded from default data collectors when SAP user names are excluded.
Unresolved RFC backends (remote services) can now be generated with verbose names. See Configure RFC Settings - Verbose Backend Names.
Application, Tier, and Node are now replicated into all custom analytics schemas that are generated by the ABAP Agent.
It is now possible to toggle ABAP Agent debug mode via t-code /DVD/APPD_STATUS. See Debug Mode.
HTTP SDK startup log file size is now limited to a specific number of lines to prevent infinite file growth.
Monitoring of RFC queues was added. For collector input settings, see Monitoring of qRFC Queues. For out-of-box dashboard details, see RFC Monitoring.
Insights for AppDynamics license does not check for system count and productive system count anymore. It only check for used server count. After this change, it is no longer required to generate special licenses to enable the monitoring of external systems as long as the original license contains sufficient amount of servers.
Insights STAD collector can now collect the top 5 used tables for background job records (TASK_TYPE = "Background") and add them to analytics schema sap_workload_transaction_profile as fields TOP_TAB1 - TOP_TAB5. The guide on how to enable the collection of top 5 used tables is available here.
Minor improvements in extension logging.
ASM-441: HTTP SDK for Windows randomly crashed with EXCEPTION_ACCESS_VIOLATION.
ASM-461: MESSAGE_TYPE_X dump occurred in custom CRM implementations.
ASM-482: STAD to Dump correlation did not work on some SAP releases because of a known SAP kernel bug.