Difference between revisions of "Seon logging"
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Logging mechanisms == | == Logging mechanisms == | ||
| − | Different technologies are used for logging | + | Different technologies are used for deep system logging situations. These are differented in the following topics: |
=== Seonapi logging === | === Seonapi logging === | ||
| Line 19: | Line 19: | ||
The position where the Seon debug daemon writes its logfiles is dependant on the Seon's configured temporary directory. Configuration options for the daemons are: | The position where the Seon debug daemon writes its logfiles is dependant on the Seon's configured temporary directory. Configuration options for the daemons are: | ||
*[[Seon_Core_configuration#temporary_directory|Temporary directory]] ("Configuration" -> "Directories" -> "Temporary directory") | *[[Seon_Core_configuration#temporary_directory|Temporary directory]] ("Configuration" -> "Directories" -> "Temporary directory") | ||
| − | *[[Seon_Core_configuration#Enable_continuous_write_of_Seon_debug_daemon_output.3F|Enable continuous write of Seon debug daemon output?]] ("Configuration" -> "Logging" -> "Enable continuous write of Seon debug daemon output? ") | + | *[[Seon_Core_configuration#Enable_continuous_write_of_Seon_debug_daemon_output.3F|Enable continuous write of Seon debug daemon output?]] ("Configuration" -> "Logging" -> "Enable continuous write of Seon debug daemon output?") |
| + | *[[Seon_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: | ||
| + | seon-logfile-<datestamp>-<timestamp>.log | ||
| + | Example: | ||
| + | /opt/seon/tmp/seon-logfile-20130604-165815.log | ||
| + | |||
| + | Every time the debug daemon writes a debug dump file, the optionally configured [[Seon_Core_configuration#debug_daemon_log_script|debug daemon log script]] is being executed. The single [[Seon_Core_event_scripts#debug_daemon_log_script|parameter]] is the absolute path of the logfile itself. Seon debug daemon logfiles can be compressed quite good (about 90% shrinking factor with gzip). | ||
| + | |||
| + | A dedicated documentation about how to [[Seon create log dumps|handle the Seon 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: [[Seon_Core_environment_variables#Database_performance_benchmarking|Database performance benchmarking]] | ||
Latest revision as of 15:10, 4 June 2013
Contents
Logging mechanisms
Different technologies are used for deep system logging situations. These are differented in the following topics:
Seonapi logging
The communication between the web interface (and the native administrative application) and the PHP backend is logged in the Seonapi logfile. The following parameters are configurable:
- absolute position of the logfile ("Configuration" -> "Logging" -> "Absolute path to logfile of Seon API")
- Seonapi loglevel ("Configuration" -> "Logging" -> "Seon API loglevel")
The default position of the logfile is:
/opt/seon/tmp/seonapi.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:
seonapi.log.1 seonapi.log.2 seonapi.log.3 seonapi.log.4
Daemon logging
When external communication is being involved for logging, the Seon 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 Seon debug daemon writes its logfiles is dependant on the Seon's configured temporary directory. Configuration options for the daemons are:
- Temporary directory ("Configuration" -> "Directories" -> "Temporary directory")
- Enable continuous write of Seon debug daemon output? ("Configuration" -> "Logging" -> "Enable continuous write of Seon debug daemon output?")
- 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:
seon-logfile-<datestamp>-<timestamp>.log
Example:
/opt/seon/tmp/seon-logfile-20130604-165815.log
Every time the debug daemon writes a debug dump file, the optionally configured debug daemon log script is being executed. The single parameter is the absolute path of the logfile itself. Seon debug daemon logfiles can be compressed quite good (about 90% shrinking factor with gzip).
A dedicated documentation about how to handle the Seon 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: Database performance benchmarking
