SAP Application Log Test

If the Error Log does not contain the required information to solve the error, administrators need to access the Application Log. The Application Log contains the steps processed when the request was executed. Each line represents one step of the request execution. Though administrators access the Application Logs in rare cases, it is the onus of the administrators to keep a vigil on the Application Logs at all times. This will help them in resolving errors as and when it occurs. By periodically scanning thee application logs for specific patterns of log entries, administrators can quickly capture errors, know when a process was spawned for the objects, and determine which subobject was error-prone frequently. This is exactly what the SAP Application Log test does.

For each subobject/application, this test periodically searches the application logs for specific patterns of error/general information messages and reports the count and nature of such messages, so as to enable administrators to troubleshoot better. This test also reports the statistical information on the events generated by the target system. using this test, administrators can determine the subobject/application that is frequently prone to errors.

Target of the test : A SAP ABAP System

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each Object:subobject associated with the target SAP ABAP System 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.
Port	Enter the port to which the specified host listens.
Connection Type	Specify how this test should connect to the target SAP ABAP System and collect the required metrics. By default, this flag is set to Application Server indicating that the test uses the IP address of a SAP ABAP Instance connected to the target SAP ABAP System to collect the required metrics. If this flag is set to Logon Group, then, the eG agent automatically connects to the logon group, chooses any one of the available SAP ABAP Instances within the group to connect to the target SAP ABAP System and collects the required metrics.
SID	Specify the three-digit server-specific unique identification code associated with the target SAP ABAP System here. The SID helps in uniquely identifying the target SAP ABAP System.
Application Server	This parameter appears only when the Connection Type flag is set to Application Server. For the eG agent to connect to the target SAP ABAP System and collect metrics, this test should be configured with the IP address of any of the SAP ABAP Instances associated with the target SAP ABAP System. Specify such IP address in this text box.
Message Server	This parameter appears only when the Connection Type flag is set to Logon Group. Specify the IP address of the SAP Message Server to which the target SAP ABAP System is connected to.
Logon Group	This parameter appears only when the Connection Type flag is set to Logon Group. A logon group is a group of servers that belongs to one SAP system. Logon groups are used to automatically distribute user logons to individual instances or to groups of SAP instances (Applications Server). Specify the name of the logon group that should be used by the eG agent to connect to any one of the SAP ABAP Instances within the group and collect the required metrics from the target SAP ABAP System.
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.
Include Objects and Subobjects	By default, this test monitors all the Objects and SubObjects of the target system. However if you wish to monitor only a few Objects and Subobjects, specify a comma-separated list of Objects and SubObjects that need to be monitored in this text box. The format is: <Objects>#<SubObjects>. For example, you can specify the Object and Subobject as End-To-End Alerting#Event Calculation Engine. You can even specify patterns of Objects and SubObjects that need to be monitored in this text box. For this, * is used to specify the pattern. Example: End-To-End , Alerting#Event, Alerting#Event Calculation Engine.
Exclude Objects and Subobjects	By default, this test monitors all the Objects and SubObjects of the target system. However if you wish to exclude one/more Objects and Subobjects, specify a comma-separated list of Objects and SubObjects that need to be monitored in this text box. The format is: <Objects>#<SubObjects>. For example, you can specify the Object and Subobject as End-To-End Alerting#Event Calculation Engine. You can even specify patterns of Objects and SubObjects that need to be monitored in this text box. For this, * is used to specify the pattern. Example: End-To-End , Alerting#Event, Alerting#Event Calculation Engine.
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
Total Logs	Indicates the total number of logs recorded for this subobject during the last measurement period.	Logs
Total messages	Indicates the total number of messages recorded for this subobject during the last measurement period.	Messages
Log rate	Indicates the rate at which logs were recorded for this subobject during the last measurement period.	Logs/min
Message rate	Indicates the rate at which messages were recorded for this subobject during the last measurement period.	Messages/min
Cancel logs	Indicates the number of logs (recorded for this subbject) that were cancelled during the last measurement period.	Logs	The detailed diagnosis of this measure if enabled, lists the Client, Log Number, External ID, Date, Time, User, TCode, Program, Mode, Importance, Log handle, DDIC Structure, Total Messages and detailed cancelled messages recorded.
Error logs	Indicates the number of logs that were error prone for this subobject during the last measurement period.	Logs	Compare the value of this measure across subobjects to determine the subbobject that is frequently prone to errors. The detailed diagnosis of this measure if enabled, lists the Client, Log Number, External ID, Date, Time, User, TCode, Program, Mode, Importance, Log handle, DDIC Structure, Total Messages and detailed error messages recorded.
Warning logs	Indicates the number of logs that contained warnings for this subobject during the last measurement period.	Logs	The detailed diagnosis of this measure if enabled, lists the Client, Log Number, External ID, Date, Time, User, TCode, Program, Mode, Importance, Log handle, DDIC Structure, Total Messages and detailed warning messages recorded.
Information logs	Indicates the number of logs with information messages recorded for this subobject during the last measurement period.	Logs	The detailed diagnosis of this measure if enabled, lists the Client, Log Number, External ID, Date, Time, User, TCode, Program, Mode, Importance, Log handle, DDIC Structure, Total Messages and detailed information messages recorded.
Success logs	Indicates the number of logs with success messages recorded for this subobject during the last measurement period.	Logs
Cancel messages	Indicates the number of log messages that were cancelled for this subobject during the last measurement period.	Messages	The detailed diagnosis of this measure if enabled, lists the Log number, Message Number, Level, Class, Timestamp and Message.
Error messages	Indicates the number of error messages recorded in the logs for this subobject during the last measurement period.	Messages	The detailed diagnosis of this measure if enabled, lists the Log number, Message Number, Level, Class, Timestamp and Message.
Warning messages	Indicates the number of warning messages recorded in the logs for this subobject during the last measurement period.	Messages	The detailed diagnosis of this measure if enabled, lists the Log number, Message Number, Level, Class, Timestamp and Message.
Information messages	Indicates the number of information messages recorded in the logs for this subobject during the last measurement period.	Messages	The detailed diagnosis of this measure if enabled, lists the Log number, Message Number, Level, Class, Timestamp and Message.
Success messages	Indicates the number of success messages recorded in the logs for this subobject during the last measurement period.	Messages	The detailed diagnosis of this measure if enabled, lists the Log number, Message Number, Level, Class, Timestamp and Message.
Very Important messages	Indicates the number of very important messages recorded in the logs for this subobject during the last measurement period.	Messages	The detailed diagnosis of this measure if enabled, lists the Log number, Message Number, Level, Class, Timestamp and Message.
Important messages	Indicates the number of important messages recorded in the logs for this subobject during the last measurement period.	Messages	The detailed diagnosis of this measure if enabled, lists the Log number, Message Number, Level, Class, Timestamp and Message.
Medium messages	Indicates the number of medium messages recorded in the logs for this subobject during the last measurement period.	Messages	The detailed diagnosis of this measure if enabled, lists the Log number, Message Number, Level, Class, Timestamp and Message.
Additional Information messages	Indicates the number of additional information messages recorded in the logs for this subobject during the last measurement period.	Messages	The detailed diagnosis of this measure if enabled, lists the Log number, Message Number, Level, Class, Timestamp and Message.