Logging - Revision history

Gordon.dye at 18:55, 17 February 2023

2023-02-17T18:55:51Z

← Older revision		Revision as of 18:55, 17 February 2023
Line 3:		Line 3:
	The '''Logging''' [[config]] statement is provided for logging configuration errors, and should be placed in [[BRConfig.sys]]:		The '''Logging''' [[config]] statement is provided for logging configuration errors, and should be placed in [[BRConfig.sys]]:

	LOGGING <loglevel>, <native OS logfile name> [, UNATTENDED] [, DEBUG_LOG_LEVEL=<integer>] [, +CONSOLE]		LOGGING <loglevel>, <native-OS-logfile-name> [, UNATTENDED] [, DEBUG_LOG_LEVEL=<integer>] [, +CONSOLE]

	[[IMAGE:Logging.png\|700px]]		[[IMAGE:Logging.png\|700px]]

Gordon.dye at 16:50, 17 February 2023

2023-02-17T16:50:32Z

← Older revision		Revision as of 16:50, 17 February 2023
Line 3:		Line 3:
	The '''Logging''' [[config]] statement is provided for logging configuration errors, and should be placed in [[BRConfig.sys]]:		The '''Logging''' [[config]] statement is provided for logging configuration errors, and should be placed in [[BRConfig.sys]]:

	LOGGING <loglevel>, <logfile> [, UNATTENDED] [, DEBUG_LOG_LEVEL=<integer>] [, +CONSOLE]		LOGGING <loglevel>, <native OS logfile name> [, UNATTENDED] [, DEBUG_LOG_LEVEL=<integer>] [, +CONSOLE]

	[[IMAGE:Logging.png\|700px]]		[[IMAGE:Logging.png\|700px]]

Laura at 20:08, 28 July 2015

2015-07-28T20:08:34Z

← Older revision		Revision as of 20:08, 28 July 2015
Line 1:		Line 1:
	As of 4.3, the debug versions of BR now expect you to use a LOGGING configuration statement. This enables BR to post exit messages during unexpected terminations.		As of 4.3, the debug versions of BR now expect you to use a LOGGING configuration statement. This enables BR to post exit messages during unexpected terminations.

	The '''Logging''' [[config]] statement is provided for logging configuration errors, and should be placed in BRConfig.sys:		The '''Logging''' [[config]] statement is provided for logging configuration errors, and should be placed in [[BRConfig.sys]]:

	LOGGING <loglevel>, <logfile> [, UNATTENDED] [, DEBUG_LOG_LEVEL=<integer>] [, +CONSOLE]		LOGGING <loglevel>, <logfile> [, UNATTENDED] [, DEBUG_LOG_LEVEL=<integer>] [, +CONSOLE]

Laura at 20:08, 28 July 2015

2015-07-28T20:08:16Z

← Older revision		Revision as of 20:08, 28 July 2015
Line 1:		Line 1:
	As of 4.3, the debug versions of BR now expect you to use a LOGGING configuration statement. This enables BR to post exit messages during unexpected terminations.		As of 4.3, the debug versions of BR now expect you to use a LOGGING configuration statement. This enables BR to post exit messages during unexpected terminations.

	The '''Logging''' [[config]] statement is provided for logging configuration errors:		The '''Logging''' [[config]] statement is provided for logging configuration errors, and should be placed in BRConfig.sys:

	LOGGING <loglevel>, <logfile> [, UNATTENDED] [, DEBUG_LOG_LEVEL=<integer>] [, +CONSOLE]		LOGGING <loglevel>, <logfile> [, UNATTENDED] [, DEBUG_LOG_LEVEL=<integer>] [, +CONSOLE]

Gordon.dye at 15:27, 18 April 2015

2015-04-18T15:27:33Z

← Older revision		Revision as of 15:27, 18 April 2015
Line 67:		Line 67:


	'''Logfile''' denotes where the logging records will be kept. Note that Logfile is a native OS filename. Second and subsequent occurrences of the LOGGING statement may omit loglevel and logfile.		'''Logfile''' denotes where the logging records will be kept. '''Note that Logfile is a native OS filename.''' Second and subsequent occurrences of the LOGGING statement may omit loglevel and logfile.

	The '''UNATTENDED''' keyword will cause BR to run in unattended mode, without a startup screen and until a program begins to await operator input, when it will exit. Config LOGGING loglevel logfile [UNATTENDED] is now supported on linux (4.2) and this will exit BR if the program starts to wait for keyboard entry.		The '''UNATTENDED''' keyword will cause BR to run in unattended mode, without a startup screen and until a program begins to await operator input, when it will exit. Config LOGGING loglevel logfile [UNATTENDED] is now supported on linux (4.2) and this will exit BR if the program starts to wait for keyboard entry.

Laura at 15:47, 23 September 2014

2014-09-23T15:47:37Z

← Older revision		Revision as of 15:47, 23 September 2014
Line 69:		Line 69:
	'''Logfile''' denotes where the logging records will be kept. Note that Logfile is a native OS filename. Second and subsequent occurrences of the LOGGING statement may omit loglevel and logfile.		'''Logfile''' denotes where the logging records will be kept. Note that Logfile is a native OS filename. Second and subsequent occurrences of the LOGGING statement may omit loglevel and logfile.

	The '''UNATTENDED''' keyword will cause BR to run in unattended mode, without a startup screen and until a program begins to await operator input, when it will exit.		The '''UNATTENDED''' keyword will cause BR to run in unattended mode, without a startup screen and until a program begins to await operator input, when it will exit. Config LOGGING loglevel logfile [UNATTENDED] is now supported on linux (4.2) and this will exit BR if the program starts to wait for keyboard entry.

	'''DEBUG_LOG_LEVEL''' (available as of [[4.3]]) specifies the log level for debugging log messages independently of the standard log level. If not specified, the Debug_Log_Level is set to the standard loglevel.		'''DEBUG_LOG_LEVEL''' (available as of [[4.3]]) specifies the log level for debugging log messages independently of the standard log level. If not specified, the Debug_Log_Level is set to the standard loglevel.

Laura: /* Logging Messages (4.3) */

2014-09-19T17:17:49Z

Logging Messages (4.3)

← Older revision		Revision as of 17:17, 19 September 2014
Line 98:		Line 98:
	The following types of messages are written to the LOGGING file:		The following types of messages are written to the LOGGING file:

	#Config error messages based on their assigned level of importance.		1. Config error messages based on their assigned level of importance.
	#DEBUG_STR() messages where message-level is equal to or less than the DEBUG_LOG_LEVEL:
			2. DEBUG_STR() messages where message-level is equal to or less than the DEBUG_LOG_LEVEL:

	{\|		{\|
	\|- valign="top"		\|- valign="top"
	\| width="10%" \| '''Log levels 0, 1, 2 and 3'''		\| width="20%" \| '''Log levels 0, 1, 2 and 3'''
	\| System generated warning messages such as OS failures and abnormal exits.		\| System generated warning messages such as OS failures and abnormal exits.
	\|		\|
	\|- valign="top"		\|- valign="top"
	\| width="10%" \| '''Log level 5 or above'''		\| width="20%" \| '''Log level 5 or above'''
	\| User Logon data, including any logon attempts.		\| User Logon data, including any logon attempts.
	\|		\|
	\|- valign="top"		\|- valign="top"
	\| width="10%" \| '''Log level 6 or above'''		\| width="20%" \| '''Log level 6 or above'''
	\| Starting a BR program, exiting.		\| Starting a BR program, exiting.
	\|		\|
Line 129:		Line 130:
	{\|		{\|
	\|- valign="top"		\|- valign="top"
	\| width="10%" \| '''Log level 11 or above'''		\| width="20%" \| '''Log level 11 or above'''
	\| Any PRINT output that goes to the console is also logged (GUI ON only).		\| Any PRINT output that goes to the console is also logged (GUI ON only).
	\|		\|
	\|- valign="top"		\|- valign="top"
	\| width="10%" \| '''Log level 12 or above'''		\| width="20%" \| '''Log level 12 or above'''
	\| TRACE, and DISPLAY messages.		\| TRACE, and DISPLAY messages.
	\|		\|
	\|- valign="top"		\|- valign="top"
	\| width="10%" \| '''Log level 13 or above''		\| width="20%" \| '''Log level 13 or above'''
	\| Lots of what the system is doing now messages.		\| Lots of what the system is doing now messages.
	\|}		\|}

Laura at 17:15, 19 September 2014

2014-09-19T17:15:37Z

@@ Line 1: / Line 1: @@
 The '''Logging''' [[config]] statement is provided for logging configuration errors:
@@ Line 6: / Line 8: @@
-'''Loglevel'''  is the maximum level of detail to be logged:
+'''Loglevel'''  is the maximum level of detail to be logged. The Logging Level is meant to specify the level of detail to be logged, with greater detail logged at higher log levels:
 {|Border=1
@@ Line 64: / Line 66: @@
 |}
 '''Logfile''' denotes where the logging records will be kept.
 The '''UNATTENDED''' keyword will cause BR to run in unattended mode, without a startup screen and until a program begins to await operator input, when it will exit.
@@ Line 89: / Line 92: @@
 Any config messages that occur before the config statement logging will be sent only to the screen.  These will cause BR to pause a few seconds so that the messages can be viewed.
-====Logging Abnormal Termination====
+===Logging Messages (4.3)===
-A new logging capability is provided for handling [[BRServer]] failures. An error log file in the BRServer directory is appended to when a BRServer process is abnormally ended. Also, a [[client]] [[msgbox]] is displayed when an [[assertion failure]] or program crash occurs. On [[Unix]] systems, the system error log is also updated. [[Keepalive]] failures are also logged here.
-As of [[4.3]] the [[debug versions of BR]] expect you to use a Logging configuration statement.
+;Examples:
 ====See Also====
 *[[Debug_Str]]
 <noinclude>

John: /* (unfiltered) BR! 4.3 Enhancments */

2014-07-02T17:39:22Z

(unfiltered) BR! 4.3 Enhancments

← Older revision		Revision as of 17:39, 2 July 2014
Line 92:		Line 92:
	A new logging capability is provided for handling [[BRServer]] failures. An error log file in the BRServer directory is appended to when a BRServer process is abnormally ended. Also, a [[client]] [[msgbox]] is displayed when an [[assertion failure]] or program crash occurs. On [[Unix]] systems, the system error log is also updated. [[Keepalive]] failures are also logged here.		A new logging capability is provided for handling [[BRServer]] failures. An error log file in the BRServer directory is appended to when a BRServer process is abnormally ended. Also, a [[client]] [[msgbox]] is displayed when an [[assertion failure]] or program crash occurs. On [[Unix]] systems, the system error log is also updated. [[Keepalive]] failures are also logged here.

	~~====(unfiltered) BR! [[4.3]] Enhancments====~~
	~~The [[debug versions of BR]] now expect you to use a LOGGING configuration statement.~~

	Message Levels are compared with Log Levels during the filtering process. The Logging Level is meant to specify the level of detail to be logged. The following types of messages are to be written to the LOGGING file:

	*Config error messages based on their assigned level of importance.
	*DEBUG_STR() messages where message-level is equal to or less than the DEBUG_LOG_LEVEL.

	~~Note that the lower the DEBUG_STR() message level, the less likely it will be filtered out of the log.~~


			As of [[4.3]] the [[debug versions of BR]] expect you to use a Logging configuration statement.

	====See Also====		====See Also====

John at 17:38, 2 July 2014

2014-07-02T17:38:03Z

← Older revision		Revision as of 17:38, 2 July 2014
Line 13:		Line 13:
	\|MAJOR_ERROR		\|MAJOR_ERROR
	\|causes major problems during execution		\|causes major problems during execution
	\|-
	~~\|1, 2 and 3~~
	\|
	~~\|System generated warning messages such as OS failures and abnormal exits.~~
	\|-		\|-
	\|1		\|1