ABAP Agent and Datavard Insights is now compatible with S/4 HANA version 1909. See SAP Supported Environments.
BSP match rule now contains the BSP event field. This enables better filtering of BSP traffic. See BSP Application Match Rule.
Analytics schema sap_workload_rfc_profile now contains new fields RFC_CALLING_INSTANCE, RFC_CALLING_IP_ADDRESS and RFC_CALLING_RELEASE. These fields are populated for records with DIRECTION = inbound and the fields help to pinpoint the exact caller.
Additional safety checks are added to ABAP Agent components that handle asynchronous endings of business transactions. These checks proactively prevent the depletion of RFC resources when system utilization is very high.
When the safety check detects abnormal behavior, asynchronous processing is temporarily switched to synchronous mode. When this occurs, ABAP trace processing is skipped to not affect end-user sessions. The corresponding 'No ABAP Trace' message is added to the business transaction snapshots.
It is now possible to toggle SQL parameter obfuscation in Top 5 SQL statements. See Configure Additional Snapshot Content Settings.
All Business Transaction errors are now also reported as 'SAP Error' data collector. When Analytics Agent is used, this data collector is reported into transaction analytics.
Native HANA databases can now be monitored using Datavard Insights. See Setup Monitoring of External Sytems with Datavard Insights and Monitor Native HANA Database.
It is now possible to generate dashboards for monitoring native HANA databases, see SAP Dashboard Generator.
License status protocol is now available under transaction code /DVD/APPD_STATUS.
Click on the icon in the connection status column to display full license protocol. Long texts are available for specific messages and provide additional information.
When no valid license is available, collecting and reporting metrics, events and analytics data is not available.
You need a valid license to be installed on each monitored system. If you have purchased AppDynamics ABAP Agent or Insights for AppDynamics and you don't have a valid license, then reach out to your AppDynamics sales representative for more information. See also Licensing options. See also Licensing options. |
Transaction code /DVD/APPD_CC makes it possible to revert all changes using the Restore Defaults toolbar button.
It is now possible to export and import the following collector settings:
See Export and Import ABAP Agent Settings.
Tree in transaction code /DVD/APPD_STATUS now shows a list of external monitored systems with the connection status of the corresponding Machine Agent HTTP listener.
Click on the icon in the connection status column to display full error protocol. Long texts are available for specific messages and provide additional information. See also Monitor Remote Machine Agent Status.
Custom event types are used in application event filtering, but it is not possible to find this custom event type through the controller GUI. Custom events now contain the 'Custom Event Type' value on the Details tab. For more information about the custom event filtering, see KPI Detail Tables.
It is now possible to correlate RFC calls to JCo Server on Java systems and applications. Client-side code adjustments are necessary for this correlation to work. See Enable Business Transaction Correlation with SAP JCo and Instrument Custom ABAP Code for more details.