Cross Component Trace is a facility of the product's logging framework that records, in the log and trace output, the information needed to trace a request as it passes through different components, threads, and even separate servers. It does this by adding correlation data, such as a request identifier, to the records. Because every record belonging to the same request carries the same identifier, an analyst can reconstruct the path of the request through the log and trace files from different sources. The correlation information is thereby added to log and trace data; it does not reduce the volume. Option D, as worded, describes the use of correlation information with the log and trace files, which is the closest to the facility's purpose among the choices, although the verb "reduce" applies more to the effort of analysis than to the size of the files.
Option A is incorrect because XCT is not a tool for analysing logs; analysis is carried out with other tools, such as the log viewers, and with XCT the data is only prepared. Option B refers to capturing data snapshots, which is the effect of the highest correlation level only, and not the general purpose. Option C is incorrect because the tracing adds overhead, so it is best used for troubleshooting, in test or targeted production investigation, and not as a permanent production setting.
The level can be set to request ID only, for the least overhead, up to full snapshots.
[Reference: Cross Component Trace (XCT); Correlation levels; Using XCT to troubleshoot applications.]
Submit