Skip to main content
Version: 2024.10

SAP ApplicationLog Monitor

Monitoring of SAP ABAP Application Log (transaction SLG1) depending on different filters.

General

ExecutableSAP ApplicationLog Monitor.exe
Connection methodRFC
Ports
  • 33$$
  • 48$$ (SNC) ($$ = Instance number)

Default parameters

Parameter namePossible valuesDefaultDescription
Host<ip> | <hostname>emptyHostname or IP of the target system. If you use a virtual hostname on your SAP servers, please use also the virtual host to connect.
SAPSIDstring (3) | XXXemptySID of the SAP system
SAPInstancenumber (2) | 00 - 99emptyInstance number of the SAP system
SAPClientnumber (3) | 000 - 999emptySAP Client (CLNT/MANDT)
SAPUsernamestringemptySAP user
SAPPasswordstringemptyPassword of the SAP user

Sensor-specific parameters

Parameter namePossible valuesDefaultDescription
Minutes60Past minutes to check
Objects&lt;object1&gt;[,&lt;object2&gt;[,&lt;object3&gt;,...]]* (all objects)Filter for objects (* can be used as wildcard)
Subobjects&lt;subobject1&gt;[,&lt;subobject2&gt;[,&lt;subobject3&gt;,...]]* (all subobjects)Filter for subobjects (* can be used as wildcard)
Users&lt;user1&gt;[,&lt;user2&gt;[,&lt;user3&gt;,...]]* (all users)Filter for users (* can be used as wildcard)
Tcodes&lt;tcode1&gt;[,&lt;tcode2&gt;[,&lt;tcode3&gt;,...]]* (all transaction codes)Filter for transaction codes (* can be used as wildcard)
Programs&lt;program1&gt;[,&lt;program2&gt;[,&lt;program3&gt;,...]]* (all programs)Filter for programs (* can be used as wildcard)
Modes&lt;mode1&gt;[,&lt;mode2&gt;[,&lt;mode3&gt;]] | (D = Dialog, B = Batch, I = Batch-Input)* (all modes)Filter for modes (* can be used as wildcard)
ExternalID&lt;id1&gt;[,&lt;id2&gt;[,&lt;id3&gt;,...]]* (all external IDs)Filter for ExternalID (* can be used as wildcard)
ProblemClassnumber | 1 - 4 (1 = Very Important, 2 = Important, 3 = Warning, 4 = Additional Information)4 (all problem classes are considered)Filter for ProblemClass, show logs with ProblemClass less or equal as set.

Channels

Channel nameDescriptionLookup file
Application Errors TotalCount of errors depending on the given filters

Important notes

warning

Depending on the monitored system, the count of entries in the application log can be huge. Check sensor execution time at command line with option --time to get an estimation. Then you can maintain the sensor timeout setting in PRTG to avoid errors. If execution time is too long, decrease parameter “Minutes”. The sensor doesn’t have predefined limits.

warning

Please check the channel limits in PRTG if they fit for your alerting.

Troubleshooting

SymptomPossible solution

Changelog

VersionChanges
2024.04Added new parameter to filter by problem class
2021.09Added new parameter to filter by ExternalID
2021.06First stable release