====== ABAP Users memory ======

  Monitors SAP ABAP user-session memory usage by instance, client, user,
  and session type. It detects sustained or immediate memory overuse,
  raises alarms with configurable severity, and can generate per-user
  memory metrics for operations and reporting.

===== What Can Be Monitored =====
  * This monitor evaluates ABAP user sessions and supports filtering by:
    * Instance
    * Client
    * Session Type
    * Users

  * Monitoring capabilities:
    * Threshold-based memory alarms (MB)
    * Duration-based alarms for sustained overuse
    * Optional notification to the affected user
    * Per-user memory metric generation

===== Monitored Data =====

The monitor uses session data such as:
  * Instance
  * Client
  * User
  * Session type
  * Memory used (MB)
  * Application/transaction context
  * Additional session info (when available)

===== Configuration hint =====

  * Use ''*'' in Instance, Client, Session Type, and Users to match all values.
  * Set Max. used memory (MB) to ''0'' to disable threshold alarming for that row.
  * Duration (Min) applies only after threshold breach is detected.
  * Alarm, Metric, and Report control output behavior per surveillance row.
  * Notify user sends alarm notifications only if user email is available.

===== Configuration =====

=== Monitoring parameters ===

^ Parameter name ^ Required ^ Default value ^ Description ^
| None | No | - | This monitor is configured only through the Surveillance Table. |

=== Surveillance Table ===

^ Parameter name ^ Required ^ Default value ^ Description ^
| Active | Yes | true | Enables or disables the row evaluation. |
| Instance | Yes | * | ABAP instance filter (supports wildcard matching). |
| Client | Yes | * | SAP client filter (supports wildcard matching). |
| Session Type | Yes | * | Session type filter (supports wildcard matching). |
| Users | Yes | * | User filter (supports wildcard matching). |
| Max. used memory (MB) | Yes | 0 | Memory threshold in MB. Alarm thresholding is active only when not 0. |
| Duration (Min) | Yes | 0 | Minimum continuous breach duration in minutes before alarming. 0 means immediate alarm. |
| Notify user | Yes | false | Adds matched user email as alarm receiver when available. |
| Severity | Yes | MAJOR | Alarm severity used when alarm conditions are met. |
| Auto clear | Yes | true | Defines whether generated alarms are clearable. |
| Alarm tag | No | (empty) | Optional alarm text prefix/tag for classification. |
| Alarm | No | true | Enables alarm generation for this row. |
| Metric | No | false | Enables metric generation for this row. |
| Report | No | false | Enables report-mode output for this row. |

===== Alarm conditions =====

An alarm is generated when all conditions are true:
  * Active is true
  * Alarm is true
  * Session matches Instance, Client, Session Type, and Users filters
  * Max. used memory (MB) is not 0 and memory usage breaches threshold
  * Duration (Min) is 0, or breach lasts longer than Duration (Min)

Alarm message includes used memory, user, instance, client, session type, and optional application/info context.

===== Generated metrics =====

^ Metric name ^ unit ^ description ^
| ABAP instance memory used per user | MB | Memory used for each matched user session, tagged with instance, client, user, session type, and transaction/application. |

===== Example =====

^ Active ^ Instance ^ Client ^ Session Type ^ Users ^ Max. used memory (MB) ^ Duration (Min) ^ Notify user ^ Severity ^ Auto clear ^ Alarm tag ^ Alarm ^ Metric ^ Report ^
| true | * | * | * | * | 500 | 0 | false | 4 | true | MEM | true | false | false |
| true | DVEBMGS00 | 100 | GUI | JDOE | 300 | 10 | true | 3 | true | HOTUSR | true | true | false |
| true | * | * | * | * | 0 | 0 | false | 4 | true | METRICONLY | false | true | false |

Resulting alarms:
  * Example row 1: immediate alarm when any matched session reaches 500 MB or more.
  * Example row 2: alarm only when JDOE stays above 300 MB for more than 10 minutes.
  * Example row 2: if user email exists, alarm notification is also sent to that user.
  * Example row 3: no alarm is generated because Alarm is false and threshold is disabled.