What are the different logging levels for Progress?

« Go Back


EnvironmentProduct: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Question/Problem Description
What are the different Logging Levels (-logginglevel)?
What does the -logginglevel startup parameter do?
What is the LOGGING-LEVEL attribute of the LOG-MANAGER system handle?
Specifying the Logging Level
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number

The logging level represents the amount of information written to the log file.

Logging level Description

0 (None)
Log no entries. This is equivalent to turning logging off.

1 (Errors)
Log OpenEdge error messages. This includes all error messages and is unrelated to the entry types specified. Errors continue to be logged at all higher levels.

2 (Basic)
Log entry types determine the logged information. Each entry type will generate at least some output. This is the default.

3 (Verbose)
Log entry types determine the logged information.

4 (Extended)
Log entry types determine the logged information.

Specifying the logging level

Specify the logging level at which log entries are written to the log file by using:

• The Logging Level (-logginglevel) startup parameter.
• The LOGGING-LEVEL attribute on the LOG-MANAGER system handle.
• The loggingLevel and related properties in the file.

By default, the logging level specified using the Logging Level (-logginglevel) startup parameter or equivalent handle attribute or ubroker property applies to all log entry types specified. However, a different logging level may be specified for each log entry type by adding the logging level to the log entry type, separated by a colon. For example, the following specifies logging level 2 for all but the 4GLTrace log entry type, which uses logging level 3:

-logentrytypes 4GLTrace:3,DynObjects.*,ProEvents.*


To turn off logging without modifying other logging characteristics, set the logging level to 0 (None). If a log file is not specified, but other logging parameters are specified, a warning is raised about this inconsistency.

The logging level selected has an impact on the performance of the system. When more detail is specified, more information must be written to the log file.

Last Modified Date9/13/2015 4:51 AM

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Was this article helpful?


Your feedback is appreciated.

Please tell us how we can make this article more useful.

Characters Remaining: 1025