Follow Requests Across Services with Traces (Beta)

Now you can follow a single request in Log Center as it travels across B2C Commerce services. The new Traces page (Beta) shows the end-to-end path of a request and the time spent in each service, so you can pinpoint where latency or errors occur without stitching together separate logs. Search traces by service and time period, open a trace to read its nested span waterfall, and share a view with a colleague through a copyable link.

Where: This change applies to B2C Commerce. The Traces feature is a closed Beta in Log Center for developers, DevOps engineers, and admins, and is enabled per realm through a feature flag.

Note The Traces feature is a pilot or beta service that is subject to the Beta Services Terms at Agreements - Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this pilot or beta service is at the Customer's sole discretion.

How: To join the closed Beta, contact Salesforce Customer Support, your Technical Account Manager (TAM), or your Customer Success Manager (CSM). After the Traces feature is enabled for your realm, open Log Center and click Traces in the header navigation bar. Search traces by service and time period, filter by realm, open a trace to read its nested span waterfall, and click Copy link to share a view with a colleague.

Note During the Beta, only a sample of requests is traced (about 5%), so not every request has a trace. Traces are retained for 5 days, so search within that window.