There is not always a clear distinction between tracing and other forms of logging, except that the term tracing is almost never applied to logging that is a functional requirement of a program (therefore excluding logging of data from an external source, such as data acquisition in a high-energy physics experiment, and write ahead logging). Logs that record program usage (such as a server log) or operating system events primarily of interest to a system administrator (see for example Event Viewer) fall in a gray area with regards to terminology. This article deals with tracing that is primarily for debugging or diagnostic purposes.
Difficulties in making a clear distinction between event logging and software tracing arise from the fact that the some of the same technologies can be used for both, and further because many of the criteria that distinguish between the two are continuous rather than discrete. The following table lists some important, but by no means precise or universal, distinctions that are used by developers to select technologies for each purpose, and that guide the separate development of new technologies in each area:
|Event logging||Software tracing|
|Consumed primarily by system administrators||Consumed primarily by developers|
|Logs "high level" information (e.g. failed installation of a program)||Logs "low level" information (e.g. a thrown exception)|
|Must not be too "noisy" (contain many duplicate events or information not helpful to its intended audience)||Can be noisy|
|A standards-based output format is often desirable, sometimes even required||Few limitations on output format|
|Event log messages are often localized||Localization is rarely a concern|
|Addition of new types of events, as well as new event messages, need not be agile||Addition of new tracing messages must be agile|
Event logging provides system administrators with information useful for diagnostics and auditing. The different classes of events that will be logged, as well as what details will appear in the event messages, are often considered early in the development cycle. Many event logging technologies allow or even require each class of event to be assigned a unique "code", which is used by the event logging software or a separate viewer (e.g., Event Viewer) to format and output a human-readable message. This facilitates localization and allows system administrators to more easily obtain information on problems that occur.
Because event logging is used to log high-level information (often failure information), performance of the logging implementation is often less important.
A special concern, preventing duplicate events from being recorded "too often" is taken care of through event throttling.
Software tracing provides developers with information useful for debugging. This information is used both during the development cycle and after the software is released. Unlike event logging, software tracing usually does not have the concept of a "class" of event or an "event code". Other reasons that event logging solutions based on event codes are inappropriate for software tracing include:
Another important consideration for software tracing is performance. Because software tracing is low-level, the possible volume of trace messages is much higher. To address performance concerns, it often must be possible for software tracing to be turned off, either at compile-time or run-time.
Other special concerns:
Appropriate for both: