Logging (computing): Difference between revisions
m Qwertyus moved page Computer data logging to Logfile |
→Examples: Rule 13 |
||
| Line 10: | Line 10: | ||
Examples of physical systems which have logging subsystems include [[process control]] systems, and [[flight data recorder|black box recorder]]s installed in aircraft. |
Examples of physical systems which have logging subsystems include [[process control]] systems, and [[flight data recorder|black box recorder]]s installed in aircraft. |
||
Many [[operating systems]] and |
Many [[operating systems]] and computer programs include some form of logging subsystem. |
||
In the simplest case, log messages are written to a log file. Most operating systems and [[software framework]]s also provide more sophisticated services for logging. One example is the ''[[syslog]] service'' (described in RFC 3164), which allows the filtering and recording of log messages to be performed by a separate dedicated subsystem, rather than placing the onus on each application to provide its own ad hoc logging system. |
In the simplest case, log messages are written to a log file. Most operating systems and [[software framework]]s also provide more sophisticated services for logging. One example is the ''[[syslog]] service'' (described in RFC 3164), which allows the filtering and recording of log messages to be performed by a separate dedicated subsystem, rather than placing the onus on each application to provide its own ad hoc logging system. |
||
Revision as of 14:53, 18 July 2013
 |
In computing, a logfile or simply log is a file that records events taking place in the execution of a system in order to provide an audit trail that can be used to understand the activity of the system and to diagnose problems. The act of keeping a logfile is called logging.
Logs are essential to understand the activities of complex systems, particularly in the case of applications with little user interaction (such as server applications).
It can also be useful to combine log file entries from multiple sources. This approach, in combination with statistical analysis, may yield correlations between seemingly unrelated events on different servers. Other solutions employ network-wide querying and reporting.
Examples
Examples of physical systems which have logging subsystems include process control systems, and black box recorders installed in aircraft.
Many operating systems and computer programs include some form of logging subsystem.
In the simplest case, log messages are written to a log file. Most operating systems and software frameworks also provide more sophisticated services for logging. One example is the syslog service (described in RFC 3164), which allows the filtering and recording of log messages to be performed by a separate dedicated subsystem, rather than placing the onus on each application to provide its own ad hoc logging system.
Interpreting
In many cases, logs are esoteric or too verbose and therefore hard to understand; they need to be subjected to log analysis in order to make sense of them. This is often done using special log analysis software.
Transaction log
Most Databases maintain some kind of transaction log. Unlike the logs described above, these logs are not mainly intended as an audit trail for later analysis, and are not (easily) human-readable. Instead, they record changes to the stored data to allow the database to recover from crashes or other errors and maintain the stored data in a consistent state.
Most database systems have both a log in the general sense described above, and a transaction log.
See also
- Common Log Format
- Data logger
- Digital traces
- Event Viewer
- Java Logging Frameworks – logging frameworks for Java
- List of web analytics software
- Log management and intelligence
- MultiTail – tool for watching logging (for UNIX)
- Pantheios logging API library
- Server log
- Syslog
- Web counter
- Web log analysis software