Trace logging

Trace logging is typically implemented to collect and record information about application failures in test or production environments. Customer support and development personnel use the information that is provided by trace logging to diagnose and solve problems.

When you enable trace logging, trace log entries are written to an output location. When the client application makes requests to the server, the logging mechanism captures information about the request and writes it to some output medium, such as a file or a console.

You can configure the logging environment to capture general information and differing levels of detail, as required to solve the problem. Note that logging is not particularly useful in measuring method duration. The act of logging itself has some performance drag on the system and might skew such measurements. If you need to collect these types of measurements, use other available profiling tools or performance analysis tools that are more suited to the purpose.

Server and Java API trace logging can be used to help diagnose problems in your application and with analysis of performance characteristics. Refer to Content Platform Engine logging for details of how to configure logging and how to access and interpret the log files produced. The .Net API does not provide tracing, and applications of that API must rely on server logging.