(DI-2211) Report to generate custom workloads KPIs

Owned by SNP
Nov 08, 2022
3 min read

In some cases, you might need to create a lot of custom KPIs for transactional workload monitoring, which should have the same definition as any (DI-2211) Collector for Workload Statistics, but with a different transaction or report name. There is a report which can be used to generate such custom KPI(s) based on any template KPI used for transactional workload monitoring. The technical name of this report is: /DVD/MON_STAT_GEN_MODULES_KPI.

When this report is executed, the following selection screen is displayed with some predefined values:

You can adjust these inputs according to your needs:

  • Name of KPI used as template - set a valid name of an existing KPI which will be used as a template KPI for new custom KPI definitions. Also, make sure that this template KPI is also defined in the collector’s (DI-2211) Collector for Workload Statistics. When provided KPI does not exist or is not defined in relevant collector’s input tables, the report is not executed as expected.

  • Pattern for KPI name - set a pattern for a generated custom KPI name(s). Make sure that a placeholder <TCODE> is defined in this pattern. This placeholder is then replaced by a name of provided transaction or report name. In case this placeholder is not defined, only one KPI with a unique name can be then generated.

  • Pattern for KPI description - set a pattern for a description of custom KPI(s). Make sure that a placeholder <TCODE> is defined in this pattern. This placeholder is then replaced by a name of provided transaction or report name. In case this placeholder is not defined, more KPIs can have the same description and this might lead to the ambiguity of KPIs.

  • List of T-Codes/Programs - provides a list of transaction or report names, which will be monitored. Please keep in mind that for each entered transaction or program name will be generated a new custom KPI. In case duplicated records are entered into this list, only one KPI will be created.

  • Test mode (no DB changes) - we recommend running this report for the first time in test mode as it does not produce any records into DB tables.

    • If test mode is checked, the list of generated KPIs with their descriptions will be displayed into the spool output, but records will be not saved into DB tables. You can first check which KPI(s) will be generated and then run this report again in non-test mode.

Output of report execution in Test mode

  • If test mode is not checked, the list of generated KPIs with their descriptions will be saved in DB tables. The report output of this report execution in non-test mode is displaying the number of generated KPIs.

Output of report execution in non-test mode

When custom KPIs are generated into customizing, they need to be assigned to any Monitoring profile as described on the page Define a Monitoring profile for a KPI.