(DI-2108) Release Notes

New features

  • ASM-512: Collector for monitoring of expiring SSL certificates (more details)

  • ASM-601: Collector for DB Triggers monitoring (more details)

  • ASM-659: Report to delete transactional data based on more detail selection (more details)

  • ASM-735: Added new parameter 'UPD_THRESHOLD' for WP information collector (/DVD/MON_CL_COL_GET_WP) (more details)

  • ASM-738: Collector for Number Ranges (more details)

Improvements

  • ASM-682: Possibility to suppress the pop-up windows when exporting/importing data in Insights

  • ASM-701: Automated detection of IP address when detecting new application servers for newly added SAP system (more details)

  • ASM-703: Adjustments in collecting logic to not update buffered tables after each collector’s execution, but only when any change was really done (to avoid any Invalidations errors in buffer synchronization logic)

  • ASM-705: Enhanced details for qRFC monitoring (more details)

  • ASM-712: Usage of Message server host (rdisp/mshost) instead of the current application server name in the System definition

  • ASM-717: Compatibility of jqCharts with Chromium browser (more details)

  • ASM-719: Adjusted length of SQL statement row to the max. length of ALV output (128 characters) to have a possibility to retrieve the whole SQL statement from the Input table

    • ASM-730: Enhanced upgrade report to consolidate defined SQL statements to the max. length of ALV output

    • ASM-734: KPI Creation wizard splits the long SQL statement according to the max. length of ALV output

Heatmap

  • ASM-720: Resolved failure of Aggregation job due to the duplicated key error

  • ASM-726: Resolved error messages for duplicated records in logs produced by ETL analysis

  • ASM-742: Added redirection into Scoper and Query Runtime Details reports from Insights cockpit (more details)

  • ASM-744: Possibility to split ADSO type into more detailed types in Scoper report (more details)

  • ASM-745: Size and Usage statistics are aggregated into cluster according to a defined time period (by default 90 days)

Resolved issues

  • ASM-688: On higher HANA releases, port ‘%03' is not reliable anymore (adjustments in HANA collectors to not select data according to '%03’ port)

  • ASM-694: Enqueue statistics have different formats on higher releases

  • ASM-696: List of Alerts is not updated in ALV output when a new system selected

  • ASM-706: No description saved for new KPI group generated via KPI Creation wizard

  • ASM-710: JCO Setup report failure when password not provided in JCO setup

  • ASM-711: Missing authorizations when starting the JMX command for BOBJ monitoring

  • ASM-712: Possible division by zero in IO Performance and CPU HANA Collectors

  • ASM-736: Some Oracle-specific KPIs are not collected when the Oracle database is on the same host as the application server

  • ASM-751: Error in processing XML body for PI Error messages (XML contains a NULL character)