Syslog errors Test

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 issues. In addition, this test reports the error messages and the warnings 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 crops up!.

Target of the test : A SAP ABAP instance

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for every SAP ABAP instance being monitored.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed
Host	Host name of the server for which the test is to be configured.
PortNo	Enter the port to which the specified host listens.
ClientName	Specify the ID of the client system as what the eG agent will be connecting to the SAP ABAP instance. To know how to determine the client ID to use, follow the instructions provided in Determining the Client ID/Name for the eG Agent to Connect to the SAP ABAP Instance.
SAPUser	Typically, to connect to a SAP ABAP instance and run tests, the eG agent requires the permissions of a SAP user who has been assigned with certain authorization objects. Ideally, you will have to create a new user role on the SAP ABAP instance for this purpose, associate the above-mentioned authorization objects with that role, and assign the new role to an existing SAP user. The procedure for the same has been provided in Creating a New User Role for Monitoring and Assigning it to a SAP User. Once the new role is assigned to a SAP user, specify the name of this user against SAPUser.
Password	The password of the specified SAPUser.
Confirm Password	Confirm the password by retyping it here.
SysNo	An indicator of the TCP/IP port at which the SAP server listens. For example, for a server that listens at port 3200, the SysNo will be ‘00’. Similarly, if the SAP server port is 3201, the SysNo will have to be specified as ‘01’. Therefore, in the SysNo text box specify the system number of the SAP server with which the specified client communicates. To know the system number for the ABAP server being monitored, follow the procedure detailed in Identifying the SAP Router String and System Number.
Router	If the SAP client with the specified ClientName exists in a network external to the SAP server, then a router will be used to enable the server-client communication. In such a case, specify the router string of the router in the Router text box. If both the client and the server exist in the same network, then specify ‘none’ against the Router text box. To know what is the SAP Router string for the ABAP server being monitored, follow the procedure detailed in Identifying the SAP Router String and System Number.
InstanceName	This is set to none by default. This implies that the eG agent automatically discovers the instance name at run time.
Timeout	Indicate the duration (in seconds) for which this test should wait for a response from the SAP ABAP instance. By default, this is set to 120 seconds.
JCO Version	The eG agent uses the SAP JCO library to connect to the SAP ABAP system and pull out metrics. To enable the eG agent to make this connection and query the metrics, you need to specify the version of the SAP JCO library that the agent needs to use. For instance, to instruct the eG agent to use JCO v2.1.19, it would suffice if you specify the ‘major version number’ alone against JCO Version – in the case of this example, this will be 2.x. Note that if you have downloaded the SAP JCO CONNECTOR files for SAP JCO version 3 from the SAP market place (as instructed by Downloading the SAP JCO Connector files Required for Monitoring ), then the JCO Version configuration should be 3.x.
IsPassive	If the value chosen is Yes, then the server under consideration is a passive server in a SAP ABAP INSTANCE cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable” by the agent if the server is not up.
CustomPatterns	Specify a comma separated list of custom patterns for which this test should report metrics for. You can specify the patterns in the PatternName:Patternstring format. However, the PatternName is optional. If the PatternName is specified, then this PatternName is displayed as the descriptor of this test in the eG monitor interface. If the PatternName is not specified, then the PatternString alone is specified as the descriptor of this test. By default, none will be displayed against this parameter.
ShowAlertsOnly	By default, this test monitors all the syslog messages logged in the syslog file. If you wish to monitor only those syslog messages for which alerts were generated in the SAP ABAP server instance, then set this flag to Yes.
SeverityCutoff	By default, each syslog message is mapped to a severity value. Specify a severity value against this text box beyond which all syslog messages are included in the scope of monitoring. By default, the value of this parameter is 49.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Transaction problems	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.
Warnings	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.
Dumps messages	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.
AS problems	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.
Memory messages	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.
Error messages	Indicates the error 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 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.
Total issues	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 Transaction problems, Warnings, Dumps messages, AS problems, Memory messages and Error messages measures.