eG Monitoring
 

Measures reported by SapB1DIAPILogTest

SAP Business One relies on two interfaces (APIs) to enable numerous integrations or add-ons:

  • SAP HANA Service Layer API provides the ability to create mobile apps aimed at SAP Business One data and services via such open core protocols as HTTP and ODATA.

  • SAP Business One DI API, on the other side, enables developers to manipulate SAP data - read, write, update, and remove it – on the database level via objects and methods.

By default, log files are created by both SAP Business One and the components with which SAP Business One is integrated such as add-ons. These log files are stored in the same directory i.e., same location of the SAP Business One installation

These log files provide a host of information which may help administrators in gauging the performance of the DI API when integrated with SAP Business One at periodic intervals. Too many errors or warnings that are logged in the log files when left unnoticed may halt the functioning of the target SAP Business One abruptly. To avoid such abrupt failures/stops, it is essential to periodically take stock of the error and warning messages logged in the DI API log files. The SapB1DIAPILogTest helps administrators in this regard!

This test monitors logs from client types that deal with DI API. These client types include :B1 Studio Shell, Java B1 logger and DTW B1 logger. The test scans these logs for specific patterns of messages and reports the count of error and general information messages that match the configured patterns. This way, the test pinpoints critical errors that the SAP Business One may have experienced recently and reveals the clients that were affected more frequently.

Outputs of the test: One set of results for the Server Abbreviation configured.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
totMsgs Indicates the total number of messages recorded during the last measurement period. Number

 
totRate Indicates the rate at which messages were recorded during the last measurement period. Messages/min

 
warnMsgs Indicates the number of warning messages recorded during the last measurement period. Number

Compare the value of this measure across the server abbreviations to identify the client for which maximum number of warning messages were recorded.

The detailed diagnosis of this measure lists the timestamp, message source, message type, message, thread ID, file, line, instance ID, message ID, application area, process ID, business object, business object ID and whether the message is customized or not.
warnRate Indicates the rate at which warning messages were recorded during the last measurement period. Messages/min

 
errMsgs Indicates the number of error log messages recorded during the last measurement period. Number

Ideally, the value of this measure should be zero.

Compare the value of this measure across the server abbreviations to identify the client that is more errorprone.

The detailed diagnosis of this measure lists the timestamp, message source, message type, message, thread ID, file, line, instance ID, message ID, application area, process ID, business object, business object ID and whether the message is customized or not.
errRate Indicates the rate at which error messages were recorded during the last measurement period. Messages/min

 
critErrMsgs Indicates the number of critical error messages recorded during the last measurement period. Number

Ideally, the value of this measure should be zero.

When a critical error occurs, SAP Business One stops.

Compare the value of this measure across the server abbreviations to identify the client for which maximum number of critical error messages were recorded. This will help administrators identify the client that is error prone more frequently.

The detailed diagnosis of this measure lists the timestamp, message source, message type, message, thread ID, file, line, instance ID, message ID, application area, process ID, business object, business object ID and whether the message is customized or not.
auditFailMsgs Indicates the number of audit failure messages i.e., the messages recorded for failed logins during the last measurement period. Number

Compare the value of this measure across the server abbreviations to identify the client for which maximum number of audit failure messages were recorded.

The detailed diagnosis of this measure lists the timestamp, message source, message type, message, thread ID, file, line, instance ID, message ID, application area, process ID, business object, business object ID and whether the message is customized or not.
noteMsgs Indicates the number of note messages i.e., additional internal log messages that were recorded during the last measurement period. Number

 
auditSuccMsgs Indicates the number of audit success messages i.e., messages recorded for successful logins during the last measurement period. Number

 
protMsgs Indicates the number of protective log messages recorded during the last measurement period. Number

 
logAlwaysMsgs Indicates the number of ‘Always-Logged’ messages recorded during the last measurement period. Number

 
fullInfoMsgs Indicates the number of full information messages recorded during the last measurement period. Number

 
traceMsgs Indicates the number of trace messages recorded during the last measurement period. Number