Pipeline tracing
The pipeline framework provides tracing capability. Pipeline tracing allows you to monitor or troubleshoot the performance of individual custom or default Commerce pipelines and blocks, running on a given instance of a Commerce Engine. When you enable pipeline tracing, it saves trace data to the Commerce Engine node log. You can access the log file at the following location: C:\inetpub\wwwroot\<CommerceShops_Sc9>\wwwroot\logs\<SCF.<YYYYMMDD>.log.<NODEGUID>.txt .
Enable pipeline tracing
Pipeline tracing is disabled by default.
To enable pipeline tracing:
-
Open the
config.jsonfile of the running Commerce Engine service where you want to trace pipelines. For example,C:\inetpub\wwwroot\<CommerceShops_Sc9>\wwwroot\config.json. -
To enable pipeline tracing, set
"PipelineTraceLoggingEnabled"totrueandLogLevelparameters toDebug.The following provides an example of logging configuration with pipeline tracing enabled:
-
To view the trace log file, open the log file
C:\inetpub\wwwroot\<CommerceShops_Sc9>\wwwroot\logs\<SCF.<YYYYMMDD>.log.<NODEGUID>.txt.
To disable pipeline tracing, set "PipelineTraceLoggingEnabled" to false .
Pipeline tracing log example
Pipeline tracing collects start time and end time information about a running pipeline and the blocks it executes. The following shows an example output of a pipeline trace log: