(DI-2402) Release Notes

Owned by Marian Vidra
Last updated: Feb 21, 2024
3 min read

New features

  • ASM-790: New KPIs related to delay and runtime statistics for scheduled background jobs since the last snapshot

    • All technical names of new KPIs start with the prefix ‘BTC_SLR*’

  • ASM-1083: New KPIs for the currently running BTC jobs

    • BTC_JOB_RUN_DUR_LONGEST_JOB - BTC Duration of the longest running job [min]

    • BTC_JOB_RUN_RUNTIME_TOTAL - BTC Total runtime of currently running jobs [min]

  • ASM-1330: Added new column for total memory consumption in detail table Work process info

    • New KPIs to store the average and maximum of the total memory used per work process

      • WP_AVG_MEMORY - Average of the total memory used per process (all servers) [MB]

      • WP_MAX_MEMORY - Maximum of the total memory used per process (all servers) [MB]

  • ASM-1346: New parameter ‘MAX_PROCESS_TO_DETAIL’ that defines how many collected requests are reported in the detail table Canceled update requests to avoid performance issues

  • ASM-1361: New parameter ‘DIA_MARK_WP_W_ZERO_RT_AS_FREE’ that defines if work process with zero runtime should be considered as a free process or not

    • New KPIs for the monitoring of work processes that are currently running or are in an ‘On hold’ state

      • WP_DIA_NUM_ONHOLD - DIA Number of 'On Hold' WPs (server)

      • WP_DIA_NUM_RUNNING - DIA Number of currently running WPs (server)

  • ASM-1362: New alert thresholds and updated descriptions for ICM-related KPIs

    • Error: ICM_USED_CONN_P_E >= 75 %; Warning: ICM_USED_CONN_P_W >= 50 %

    • Error: ICM_USED_QUE_P_E >= 75 %; Warning: ICM_USED_QUE_P_W >= 50 %

    • Error: ICM_USED_THR_P_E >= 75 %; Warning: ICM_USED_THR_P_W >= 50 %

  • ASM-1366: Added new item ‘Download logs’ into the ‘Monitor’ menu

  • ASM-1393: New alert thresholds defined for CPU loads-related KPIs

    • Error: CPU_LOAD1_P_E >= 300 %; Warning: CPU_LOAD1_P_W >= 200 %

    • Error: CPU_LOAD1_P_SYS_MAX_E >= 300 %; Warning: CPU_LOAD1_P_SYS_MAX_W>= 200 %

    • Error: CPU_LOAD5_P_E >= 300 %; Warning: CPU_LOAD5_P_W >= 200 %

    • Error: CPU_LOAD5_PMAX_E >= 300 %; Warning: CPU_LOAD5_PMAX_W >= 200 %

    • Error: DB_CPU_LOAD5_P_E >= 300 %; Warning: DB_CPU_LOAD5_P_W >= 200 %

  • ASM-1399: New parameter ‘ONLY_NOT_STARTED_AS_DELAYED’ that controls if only not started BTC jobs should be reported into the KPI for the number of all delayed jobs

  • ASM-1405: New alert threshold defined for KPI for number of failed CB Monitoring jobs

    • Warning BTC_MON_JOB_NUM_FAILED_W >= 1 count

Improvements

  • ASM-1282: Collector for RFC ping tests was adjusted not to raise any message if no records are defined in the input table

  • 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-1318: The function to start default monitoring was adjusted to schedule all default monitoring profiles according to their predefined monitoring areas that are also supported by the monitored system

    • Added logic in XPRA report to consolidate existing monitoring areas for default monitoring profiles

  • ASM-1372: Collector for HANA Thread Info was adjusted to report correct data on HANA SPS7 for total “JobWorker” threads per host

    • In HANA SPS7 the thread type “Request” was changed to type “JobWorker” for thread method “_IDX_BackupExecutor”

  • ASM-1392: Updated short descriptions for Oracle Session-related KPIs

  • ASM-1397: Removed dependencies between CB Monitoring and Reuse Library (except product class) as preparation for SAP certification for CB Monitoring and AppDynamics ABAP Agent

    • ASM-1374: Refactoring of log manager into CB Monitoring package to remove dependencies with Reuse Library

    • ASM-1377: Refactoring of runtime calculation functionality into CB Monitoring package to remove dependencies with Reuse Library

  • ASM-1398: Consolidation of KPI unit for seconds to use only one common notation ‘sec’ in all KPI definitions

  • ASM-1416: Added a new column for external ID in the detail table for Application logs

Resolved issues

  • ASM-1268: Wrong column names defined for detail table “aRFC resource errors”

  • ASM-1341: The functionality to stop monitoring for the selected system did not stop all scheduled collector jobs

  • ASM-1342: System metrics-related KPIs for Oracle database monitoring were not collected due to the missing “ORACLENODE” external server type.

  • ASM-1355: Error occurred in the KPI creation wizard if any database function was used for modifying the date/time-related placeholder values

  • ASM-1359: Runtime error “GETWA_NOT_ASSIGNED_RANGE” occurred while using search help for existing DB connections on screens to add a new HANA or Oracle database system

  • ASM-1367: An invalid count of messages is displayed in the view for non-aggregated messages if switched from the aggregated view.

  • ASM-1376: Exception ‘CX_SY_CONVERSION_CODEPAGE' occurred while reporting data from the detail table “Erroneous queues details”.

  • ASM-1388: Invalid information available in the documentation for the Collector for qRFC queue details

  • ASM-1391: Failure of the collector due to the conflict of various data types while handling the overflow issue for the KPI value

  • ASM-1400: KPI for total free physical memory including FS cache was not collected due to the renaming of MTE class “MemoryMO_FreeInclfsCache” into “MemoryMO_FreeInclfsCach” since SAP_BASIS 756 release

  • ASM-1401: Invalid percentage value calculated for the HANA-related KPI “HDB_LOG_BUFWAITP HANA - Log buffer switches wait on buffer sem. (max all host)”

    • Invalid delta values calculated and reported in detail table “HANA log buffer details” for switch wait and no wait counts