Use Log Center to debug production issues for sites built using Storefront Next. Log Center aggregates logs from Managed Runtime (MRT) and your B2C Commerce instance in one place.
Log Center:
5xx), which help you troubleshoot content delivery and performance issues.Note
For information about the Storefront Next structured logger and log levels, see Logging in Storefront Next.
To access MRT logs for an environment in Log Center, first:
Have the Log Center User role in Account Manager. To verify, check your role in Account Manager. If you don’t have the role, ask your Account Manager admin to give you access. See Managing Account Manager for Salesforce B2C Commerce Users.
Create an environment. See Create an Environment in Business Manager.
Creating an environment in Business Manager associates the B2C Commerce instance and site IDs to the environment, which are prerequisites for Log Center logging.
Enable Log Center logs and Log Center metrics under Observability in Environment Settings. [DOUBLE CHECK THIS]
After you complete the Prerequisites, to view MRT logs in Log Center:
Open Log Center.
Select a Region.
Select a Realm. If you don’t know your realm ID, ask your Salesforce account executive (AE) or customer success manager (CSM).
Click Show filtered results.
Click Search > Current Search.
Under Service Type, select mrt for Managed Runtime logs.
Under Request Type, select SSR for application logs or CDN for CDN logs.
Under Host, select the environment whose logs you want to see. The format of the host is $PROJECT.$ENVIRONMENT. If you have more than one MRT environment with Log Center logs enabled, you see multiple MRT host names.
View the MRT logs.
Storefront Next emits logs in structured JSON format—one JSON object per line. Each line includes these fields.
| Field | Description |
|---|---|
level | Log severity: error, warn, info, or debug. |
msg | The log message. |
correlationId | A unique ID assigned per request. All log entries for a single request share the same correlationId, so you can trace a request end to end. |
method | The HTTP method, for example, GET or POST. |
path | The URL pathname of the request. |
For example:
1{
2 "level": "warn",
3 "correlationId": "a1b2c3",
4 "method": "GET",
5 "path": "/product/25518447M",
6 "msg": "Product not found"
7}To narrow results to a specific request, filter on correlationId. To narrow results to a specific route, filter on path or method.
The log level defaults to warn in production and info in other environments. The SFCC_LOG_LEVEL environment variable controls the log level. If you don’t see expected log entries, check that the log level for your environment is set appropriately. See Configure the Log Level.
Note
(Optional) Generate logs for a specific component or third-party integration by using a custom field to make log filtering easier. Log Center lets you filter on the custom field to find all logs from a specific area of your codebase.
For server-side code in loaders, actions, or middleware, use getLogger(context). In this example, the custom field in the log call is component.
1import { getLogger } from "@/lib/logger.server";
2
3export async function loader({ context }: LoaderFunctionArgs) {
4 const logger = getLogger(context);
5 if (err.code === "MISSING_DESCRIPTION") {
6 logger.warn("Missing description", {
7 component: "CmsProductDescription",
8 errorCode: err.code,
9 });
10 }
11}For module-scope or client-side code where router context isn’t available, use createLogger():
1import { createLogger } from "@/lib/logger";
2
3const logger = createLogger({ component: "CmsProductDescription" });
4logger.warn("Missing description", { errorCode: err.code });In both cases, the component field, or any custom field you add, appears in every log line and is searchable in Log Center.
j