ABAP system monitoring detecting PRIV modes

When you system has too many PRIV modes, it is about to fall over. This situation must be detected and acted upon.

You can create a custom monitoring metric to measure and act on this.

Creation of the custom metric for detecting PRIV modes

Create a custom metric following the steps in this blog. The template to be adjusted is the technical system SAP ABAP 7.10 and higher template.

Don’t forget to tick it on for monitoring otherwise it is not active.

In expert mode create a custom metric.

Create technical name Z_METRIC_DIA_WP_PRIV:

Now setup the definition for the data collection:

This will collect the PRIV dialog processes in percentage.

Mark the custom metric as relevant for monitoring:

And set the usage:

Last but not least: you need to set the alerting threshold:

Save the custom metric and make sure the template reassignment is done to activate the custom metric for your systems.

Author: Frank Umans

Working in SAP since 1998. Started as ABAP developer and later moved to SAP basis and authorizations. Since 2020 working with SAP Focused Run.

4 thoughts on “ABAP system monitoring detecting PRIV modes”

  1. To know how to Create custom metric for Abap dump , which can be used to setup the Alert whenever the specific dump only appears in the system (Example TIME_OUT, Raise_Exception Etc…)

    1. Hi Chidam,

      An idea that will work: a dump can not only be seen in the ST22 dump log, but in SM21 as well with code AB0. Example: “Runtime error “SYSTEM_NO_ROLL” occurred.” as text.
      You can check the blog on TBTCO overflow on how you can set up custom metric to read SM21 for specific code and text combination: https://www.sapfocusedrunguru.com/system-monitoring/system-monitoring-custom-metric-for-errors-in-table-locking-of-tbtco/.
      In your case you would take code AB0 and the text of your dump you need to monitor and alert on.

      Will check later if the dump extractor itself will give the require level of detail.

Leave a Reply

Your email address will not be published.