|
Measures reported by AsAbapSyslgTest
The SysLog aka “System Logging” is a text file where selected events and problems within a SAP ABAP instance are generally logged.
This test monitors the syslog file and for each event type logged into the file, this test reports the numerical statistics of the total number of messages logged, the messages that were entered due to transaction problems, application server and memory related isssues. In addition, this test reports the error messages and the warings that were entered. This way, administrators may identify the event type that is more error prone and take remedial measures to rectify the same before any severe issue crop up!.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| transactionsproblems |
Indicates the number of messages of this type entered in the syslog file with transaction problems during the last measurement period. |
Number |
Transaction problems indicate problems while invoking transaction codes.
The detailed diagnosis of this measure if enabled, lists the details such as the user executing the Tcode, the client, the terminal logged in by the user, program that is currently executing, timestamp of the problem message, severity and alert message and the actual problem message. |
| noofwarnings |
Indicates the number of warning messages of this type that were entered in the syslog file during the last measurement period. |
Number |
The detailed diagnosis of this measure if enabled, lists the details such as the user executing the Tcode, the client, the terminal logged in by the user, program that is currently executing, timestamp of the problem message, severity and alert message and the actual problem message. |
| dumpsproblems |
Indicates the number of dump messages of this type that were entered in the syslog file during the last measurement period. |
Number |
The detailed diagnosis of this measure if enabled, lists the details such as the user executing the Tcode, the client, the terminal logged in by the user, program that is currently executing, timestamp of the problem message, severity and alert message and the actual problem message. |
| asProblems |
Indicates the number of application server problem messages of this type that were entered in the syslog file during the last measurement period. |
Number |
Use these messages to trace problems that occurred when the application server was operated.
The detailed diagnosis of this measure if enabled, lists the details such as the user executing the Tcode, the client, the terminal logged in by the user, program that is currently executing, timestamp of the problem message, severity and alert message and the actual problem message. |
| memoryProblems |
Indicates the total number of memory related messages of this type that were entered in the syslog file during the last measurement period. |
Number |
Use these messages to identify memory related issues with the SAP ABAP instance.
The detailed diagnosis of this measure if enabled, lists the details such as the user executing the Tcode, the client, the terminal logged in by the user, program that is currently executing, timestamp of the problem message, severity and alert message and the actual problem message. |
| noOfErrors |
Indicates the error messages of this type that were entered ni the syslog file during the last measurement period. |
Number |
The detailed diagnosis of this measure if enabled, lists the name of the user executing the Tcode, the client, the terminal logged in by the user, Program that is currently executing, Timestamp, severity and alert message and the actual problem message. |
| allerrors |
Indicates the total number of messages of this type available in the syslog file during the last measurement period. |
Number |
This measure is a good indicator of the issues occurring on the SAP instance.
The value of this measure is cumulative of the transactionsproblems, noofwarnings, dumpsproblems, asProblems, memoryProblems and noOfErrors measures. |
|