OS4X logging - Revision history

Admin at 15:10, 4 June 2013

2013-06-04T15:10:03Z

Admin at 15:09, 4 June 2013

2013-06-04T15:09:56Z

Admin at 15:07, 4 June 2013

2013-06-04T15:07:19Z

Admin at 15:07, 4 June 2013

2013-06-04T15:07:00Z

Admin at 15:01, 4 June 2013

2013-06-04T15:01:54Z

Admin at 15:00, 4 June 2013

2013-06-04T15:00:23Z

Admin at 14:56, 4 June 2013

2013-06-04T14:56:46Z

Admin at 14:56, 4 June 2013

2013-06-04T14:56:29Z

Admin: New page: == Logging mechanisms == Different technologies are used for logging differnt communication situations. These are differented in the following topics. === OS4Xapi logging === The communic...

2013-06-04T14:51:06Z

New page: == Logging mechanisms == Different technologies are used for logging differnt communication situations. These are differented in the following topics. === OS4Xapi logging === The communic...

New page

== Logging mechanisms ==
Different technologies are used for logging differnt communication situations. These are differented in the following topics.

=== OS4Xapi logging ===
The communication between the web interface (and the native administrative application) and the PHP backend is logged in the OS4Xapi logfile. The following parameters are configurable:
*[[OS4X_Core_configuration#Absolute_path_to_logfile_of_OS4X_API|absolute position of the logfile]] ("Configuration" -> "Logging" -> "Absolute path to logfile of OS4X API")
*[[OS4X_Core_configuration#OS4X_API_loglevel|OS4Xapi loglevel]] ("Configuration" -> "Logging" -> "OS4X API loglevel")
The default position of the logfile is:
/opt/os4x/tmp/os4xapi.log
The logfile writer creates up to 6 files with a maximum filesize of 10MB, the actually used logfile is the configured one. Older logfiles have number suffixes like:
os4xapi.log.1
os4xapi.log.2
os4xapi.log.3
os4xapi.log.4

@@ Line 1: / Line 1: @@
 == Logging mechanisms ==
-Different technologies are used for deep system logging situations. These are differented in the following topics.
+Different technologies are used for deep system logging situations. These are differented in the following topics:
 === OS4Xapi logging ===

← Older revision		Revision as of 15:07, 4 June 2013
Line 32:		Line 32:

	=== Database performance logging ===		=== Database performance logging ===
−	If you suspect a database environment to be slow, an environment variable lets you control where to log all database statement performance information: [[OS4X_Core_environment_variables#Database_performance_benchmarking]]	+	If you suspect a database environment to be slow, an environment variable lets you control where to log all database statement performance information: [[OS4X_Core_environment_variables#Database_performance_benchmarking\|Database performance benchmarking]]

← Older revision		Revision as of 15:07, 4 June 2013
Line 30:		Line 30:

	A dedicated documentation about how to [[OS4X create log dumps\|handle the OS4X debug daemon is available here]].		A dedicated documentation about how to [[OS4X create log dumps\|handle the OS4X debug daemon is available here]].
		+
		+	=== Database performance logging ===
		+	If you suspect a database environment to be slow, an environment variable lets you control where to log all database statement performance information: [[OS4X_Core_environment_variables#Database_performance_benchmarking]]

← Older revision		Revision as of 15:01, 4 June 2013
Line 28:		Line 28:

	Every time the debug daemon writes a debug dump file, the optionally configured [[OS4X_Core_configuration#debug_daemon_log_script\|debug daemon log script]] is being executed. The single [[OS4X_Core_event_scripts#debug_daemon_log_script\|parameter]] is the absolute path of the logfile itself. OS4X debug daemon logfiles can be compressed quite good (about 90% shrinking factor with gzip).		Every time the debug daemon writes a debug dump file, the optionally configured [[OS4X_Core_configuration#debug_daemon_log_script\|debug daemon log script]] is being executed. The single [[OS4X_Core_event_scripts#debug_daemon_log_script\|parameter]] is the absolute path of the logfile itself. OS4X debug daemon logfiles can be compressed quite good (about 90% shrinking factor with gzip).
		+
		+	A dedicated documentation about how to [[OS4X create log dumps\|handle the OS4X debug daemon is available here]].

← Older revision		Revision as of 15:00, 4 June 2013
Line 20:		Line 20:
	*[[OS4X_Core_configuration#temporary_directory\|Temporary directory]] ("Configuration" -> "Directories" -> "Temporary directory")		*[[OS4X_Core_configuration#temporary_directory\|Temporary directory]] ("Configuration" -> "Directories" -> "Temporary directory")
	*[[OS4X_Core_configuration#Enable_continuous_write_of_OS4X_debug_daemon_output.3F\|Enable continuous write of OS4X debug daemon output?]] ("Configuration" -> "Logging" -> "Enable continuous write of OS4X debug daemon output?")		*[[OS4X_Core_configuration#Enable_continuous_write_of_OS4X_debug_daemon_output.3F\|Enable continuous write of OS4X debug daemon output?]] ("Configuration" -> "Logging" -> "Enable continuous write of OS4X debug daemon output?")
		+	*[[OS4X_Core_configuration#debug_daemon_log_script\|debug daemon log script]] ("Configuration" -> "Events" -> "debug daemon log script")
		+
		+	The temporary output is the directory where the logfiles are written in. The filename schema is:
		+	os4x-logfile-<datestamp>-<timestamp>.log
		+	Example:
		+	/opt/os4x/tmp/os4x-logfile-20130604-165815.log
		+
		+	Every time the debug daemon writes a debug dump file, the optionally configured [[OS4X_Core_configuration#debug_daemon_log_script\|debug daemon log script]] is being executed. The single [[OS4X_Core_event_scripts#debug_daemon_log_script\|parameter]] is the absolute path of the logfile itself. OS4X debug daemon logfiles can be compressed quite good (about 90% shrinking factor with gzip).

@@ Line 19: / Line 19: @@
 The position where the OS4X debug daemon writes its logfiles is dependant on the OS4X's configured temporary directory. Configuration options for the daemons are:
 *[[OS4X_Core_configuration#temporary_directory|Temporary directory]] ("Configuration" -> "Directories" -> "Temporary directory")
-*[[OS4X_Core_configuration#Enable_continuous_write_of_OS4X_debug_daemon_output.3F|Enable continuous write of OS4X debug daemon output?]] ("Configuration" -> "Logging" -> "Enable continuous write of OS4X debug daemon output? ")
+*[[OS4X_Core_configuration#Enable_continuous_write_of_OS4X_debug_daemon_output.3F|Enable continuous write of OS4X debug daemon output?]] ("Configuration" -> "Logging" -> "Enable continuous write of OS4X debug daemon output?")

← Older revision		Revision as of 14:56, 4 June 2013
Line 13:		Line 13:
	os4xapi.log.3		os4xapi.log.3
	os4xapi.log.4		os4xapi.log.4
		+
		+	=== Daemon logging ===
		+	When external communication is being involved for logging, the OS4X debug daemon collects all information of all running programs and saves them into a ring buffer. This means, that older log entries are eliminated by newer log entries, the more activity is being logged, the less is the timeframe for the actual memory content. In order to analyze special situations, it may be interesting to collect all information.
		+
		+	The position where the OS4X debug daemon writes its logfiles is dependant on the OS4X's configured temporary directory. Configuration options for the daemons are:
		+	*[[OS4X_Core_configuration#temporary_directory\|Temporary directory]] ("Configuration" -> "Directories" -> "Temporary directory")
		+	*[[OS4X_Core_configuration#Enable_continuous_write_of_OS4X_debug_daemon_output.3F\|Enable continuous write of OS4X debug daemon output?]] ("Configuration" -> "Logging" -> "Enable continuous write of OS4X debug daemon output? ")