Content deleted Content added
removing unlinked entry; fmt |
m Reverted edit by 2806:2F0:5501:F1B3:1858:EC3D:2B13:7691 (talk) to last version by Materialscientist |
||
| (38 intermediate revisions by 32 users not shown) | |||
Line 3:
{{distinguish|Data logger}}
In [[computing]], '''logging''' is the act of keeping a [[wikt:log#Etymology 2|log]] of [[Event (computing)|events]] that occur in a computer system, such as problems, errors or
In the simplest case, messages are written to a file, called a
|archive-date= February 14, 2018}}</ref> Alternatively, the messages may be written to a dedicated logging system or to a
Specifically, a
Many operating systems, software frameworks and programs include a logging system. A widely used logging standard is [[Syslog]], defined in
==
=== Event logs ===
They are essential to understand It can also be useful to combine log file entries from multiple sources.
=== Transaction logs ===
{{Main|Transaction log}}
Most [[Database|database systems]] maintain some kind of
The use of data stored in transaction logs of Web search engines, Intranets, and Web sites can provide valuable insight into understanding the information-searching process of online searchers.<ref>{{cite journal | last=Jansen
▲The use of data stored in transaction logs of Web search engines, Intranets, and Web sites can provide valuable insight into understanding the information-searching process of online searchers.<ref>Jansen, B. J. 2006. Search log analysis: What is it; what's been done; how to do it. Library and Information Science Research, 28(3), 407-432</ref> This understanding can enlighten information system design, interface development, and devising the information architecture for content collections.
=== Message logs ===
[[Internet Relay Chat|Internet Relay Chat (IRC)]], [[Instant messaging|instant messaging (IM)]] programs, [[peer-to-peer]] file sharing clients with chat functions, and [[Multiplayer video game|multiplayer]] games (especially [[MMORPG]]s) commonly have the ability to automatically save textual communication, both public (IRC channel/IM conference/MMO public/party chat messages) and private chat between users, as message logs.<ref>{{Cite web|url=https://learn.microsoft.com/en-us/dotnet/api/microsoft.sqlserver.management.smo.logfile?view=sql-smo-preview|title=LogFile Class (Microsoft.SqlServer.Management.Smo)|website=learn.microsoft.com}}</ref>
Message logs are almost universally plain text files, but IM and [[VoIP]] clients (which support textual chat, e.g. Skype) might save them in [[HTML]] files or in a custom format to ease reading or enable [[encryption]].
In the case of IRC software, message logs often include system/server messages and entries related to channel and user changes (e.g. topic change, user joins/exits/[[List of Internet Relay Chat commands#KICK|kicks]]/[[Block (Internet)|bans]], [[nickname]] changes, the user status changes), making them more like a combined message/event log of the channel in question, but such a log
Instant messaging and VoIP clients often offer the chance to store encrypted logs to enhance the user's privacy. These logs require a password to be decrypted and viewed, and they are often handled by their respective writing application. Some privacy focused messaging services, such as [[Signal (
▲In the case of IRC software, message logs often include system/server messages and entries related to channel and user changes (e.g. topic change, user joins/exits/[[List of Internet Relay Chat commands#KICK|kicks]]/[[Block (Internet)|bans]], [[nickname]] changes, the user status changes), making them more like a combined message/event log of the channel in question, but such a log isn't comparable to a true IRC server event log, because it only records user-visible events for the time frame the user spent being connected to a certain channel.
===Server
▲Instant messaging and VoIP clients often offer the chance to store encrypted logs to enhance the user's privacy. These logs require a password to be decrypted and viewed, and they are often handled by their respective writing application. Some privacy focused messaging services, such as [[Signal (software)|Signal]], record minimal logs about users, limiting their information to connection times.<ref>{{cite web|last1=Brandom|first1=Russell|title=Iran blocks encrypted messaging apps amid nationwide protests|url=https://www.theverge.com/2018/1/2/16841292/iran-telegram-block-encryption-protest-google-signal|website=The Verge|publisher=Vox Media|access-date=23 March 2018|date=2 January 2018|archive-date=11 December 2022|archive-url=https://web.archive.org/web/20180322015257/https://www.theverge.com/2018/1/2/16841292/iran-telegram-block-encryption-protest-google-signal|url-status=live}}</ref>
[[File:Apache Log.png|thumb|Apache access log showing Wordpress vulnerability bots]]
A '''server log''' is a log file (or several files) automatically created and maintained by a [[Server (computing)|server]] consisting of a list of activities it performed.▼
▲A
A typical example is a [[Webserver directory index|web server]] log which maintains a history of page requests. The [[World Wide Web Consortium|W3C]] maintains a standard format (the [[Common Log Format]]) for web server log files, but other proprietary formats exist.<ref name="auto"/> Some servers can log information to computer readable formats (such as [[JSON]]) versus the human readable standard.<ref>{{Cite web|url=https://caddyserver.com/|title=How Logging Works - Caddy Documentation|first=Caddy Web|last=Server|website=caddyserver.com}}</ref> More recent entries are typically appended to the end of the file. Information about the request, including [[client (computing)|client]] [[IP address]], request [[Calendar date|date]]/[[time]], [[webpage|page]] requested, [[HTTP]] code, bytes served, [[user agent]], and [[HTTP referrer|referrer]] are typically added. This data can be combined into a single file, or separated into distinct logs, such as an access log, [[error]] log, or referrer log. However, server logs typically do not collect user-specific information.▼
▲A typical example is a [[Webserver directory index|web server]] log which maintains a history of page requests. The [[World Wide Web Consortium|W3C]] maintains a standard format (the [[Common Log Format]]) for web server log files, but other proprietary formats exist.<ref name="auto"/> Some servers can log information to computer readable formats (such as [[JSON]]) versus the human readable standard.<ref>{{Cite web|url=https://caddyserver.com/|title=How Logging Works - Caddy Documentation|first=Caddy Web|last=Server|website=caddyserver.com}}</ref> More recent entries are typically appended to the end of the file. Information about the request, including [[client (computing)|client]] [[IP address]], request [[Calendar date|date]]/[[time]], [[webpage|page]] requested, [[HTTPs|HTTP]] code, bytes served, [[user agent]], and [[HTTP referrer|referrer]] are typically added. This data can be combined into a single file, or separated into distinct logs, such as an access log, [[error]] log, or referrer log. However, server logs typically do not collect user-specific information.
These files are usually not accessible to general Internet users, only to the [[webmaster]] or other administrative person of an Internet service. A statistical analysis of the server log may be used to examine traffic patterns by time of day, day of week, referrer, or user agent. Efficient web site administration, adequate hosting resources and the fine tuning of sales efforts can be aided by analysis of the web server logs.
== See also ==
* {{annotated link|Log management}}
▲* [[Digital traces]]
* {{annotated link|Logging as a service}}
* {{annotated link|XML log}}
* {{section link|Tracing_(software)#Event_logging}} - comparing software tracing with event logging
* {{section link|Security event management#Event logs}} - with a focus on security management
== References ==
{{refs}}
{{Authority control}}
| |||