eG Monitoring
 

Measures reported by SapB1BizLogTest

SAP Business One lets you log and trace events at the business level and the system information level during application execution. The information is saved as log messages in log files. These log files helps you in understanding the root of any issues when you are working with the application and with add-ons.

SAP Business One creates a new log file on every startup. A log file contains text information about important events that happened within the SAP Business One code. The events are written into the text file together with information about the following:

  • The time at which the event happened

  • The exact source code line the event refers to

  • The event’s message content

The log files have a unique, predefined name that contains a date, a time stamp, and the Process ID (PID) of the SAP Business One application that created the file. Tracing and logging information, all types of event levels, and severity levels are stored together in one log file.

The log file size is restricted to a default maximum value in terms of MB. After the file exceeds the maximum size, SAP Business One creates a new file. The number of log files that can be stored in a logging directory depends on the configuration of the folder size.

This test monitors logs from client types that deal with business and technical information in general. These client types include : B1 Logger, AuditLogger, StartupLogger, Stock Tool, DTW B1 Logger and Java based 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

Ideally, the value of this measure should be zero.

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

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.

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 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