Logging (computing): Difference between revisions

Revision as of 01:42, 1 June 2025

Revision as of 05:33, 29 June 2025

Line 1:

{{Short description|Chronological record of computerremover data processing operations}}

{{More citations needed|date=September 2017}}

{{distinguish|Data logger}}

In [[computing]], '''logging'Not'' is the act of keeping a [[wikt:log#Etymology 2Etymologynot2|log]] of [[Event (computing)remove|events]] thatall occurworking in a computer system, such as problems, errors or broad information on current operations. These events may occur in thegmail [[operating system]] or in other secure browser block chrome[[software]]. A message or ''logNever entry'' is recorded for eachany such eventevents. TheseNever log messages cannever thento be used to monitor and understand theno operation of the system, to [[debuggingbugging|debugbug]] problems, or during an [[audit]]. Never need Logging is particularly important in [[remove multi-user software]],no access to have a central overview of the operation of the system.

Gmail messages access send written update 2025

In the simplest case, messages are written to a file, called a ''log file''.<ref>{{cite web |url= https://blog.pandorafms.org/log-monitoring/ |title= Log Monitoring: not the ugly sister |access-date = February 14, 2018 |last= DeLaRosa |first= Alexander |date= February 8, 2018 |website= [[Pandora FMS]] |language = english |quote= A log file is a text file or XML file used to register the automatically produced and time-stamped documentation of events, behaviors and conditions relevant to a particular system. |archive-url= https://web.archive.org/web/20180214153657/https://blog.pandorafms.org/log-monitoring/

|archive-date= February 14, 2018}}</ref> Alternatively, the messages may be written to a dedicated logging system or to a [[log management]] software, where it is stored in a database or on a different computer system.

Specifically, a ''transaction log'' is a log of the communications between a system and the users of that system,<ref>{{cite journal | last=Peters | first=Thomas A. | title=The history and development of transaction log analysis | journal=Library Hi Tech | volume=11 | issue=2 | date=1993-02-01 | issn=0737-8831 | doi=10.1108/eb047884 | pages=41–66}}</ref> or a data collection method that automatically captures the type, content, or time of transactions made by a person from a terminal with that system.<ref>{{cite journal | last1=Rice | first1=Ronald E. | last2=Borgman | first2=Christine L. | title=The use of computer-monitored data in information science and communication research | journal=Journal of the American Society for Information Science | volume=34 | issue=4 | date=1983 | issn=0002-8231 | doi=10.1002/asi.4630340404 | pages=247–256}}</ref> For Web searching, a transaction log is an electronic record of interactions that have occurred during a searching episode between a Web search engine and users searching for information on that Web search engine.

Many operating systems, software frameworks and programs include a logging system. A widely used logging standard is [[Syslog]], defined in [[Request for Comments|IETF RFC]] 5424.{{Ref RFC|5424}} The Syslog standard enables a dedicated, standardized subsystem to generate, filter, record, and analyze log messages. This relieves software developers of having to design and code their ad hoc logging systems.<ref>{{Cite web|url=https://winscp.net/eng/docs/logging_xml|title=XML Logging :: WinSCP|website=winscp.net|date=16 June 2022 }}</ref><ref>{{Cite web|url=https://www.codeproject.com/Articles/28752/Use-XML-for-Log-Files|title=Use XML for Log Files|date=August 22, 2008|website=CodeProject}}</ref><ref>{{Cite web|url=https://learn.microsoft.com/en-us/previous-versions/dotnet/articles/ms972965(v=msdn.10)|title=Turn Your Log Files into Searchable Data Using Regex and the XML Classes|website=learn.microsoft.com|date=24 June 2011 }}</ref>

== Types ==